PopulaceLab (test)
Offline 24.8.85.119:28335 checked 14h ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 20:37 UTC1d ago | – | – | running | 0 |
| Sat 24 Oct, 21:38 UTC3d ago | 0 | – | 2 days | 0 |
| Sat 17 Oct, 18:27 UTC11d ago | 1 | – | 7.1 days | 0 |
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 157 on average | 205 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50 / 1000 |
Quick answers
from the figures on this pageWipe data
On what cycle does PopulaceLab (test) wipe?
The next wipe on PopulaceLab (test) cannot be predicted, because it wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 45 hours ago.
Wipe day on PopulaceLab (test): what should you expect?
Recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe the crowd peaked.
Server
Which location hosts PopulaceLab (test)?
No region appears in what PopulaceLab (test) publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 24.8.85.119:28335.
What Rust build does PopulaceLab (test) run?
Rust network protocol 2635 and build 168909 on Windows is the setup for PopulaceLab (test). The protocol has to match before you can join; Steam updates it automatically.
How reliable is PopulaceLab (test), and is it online now?
Offline at this refresh: PopulaceLab (test), last seen 14 hours ago. The uptime it reports puts the last restart at about 31 hours ago. 18% uptime over the last 7 full days, equal to 30 of 168 hours. 17 October 2026 is when Rust Server Analytics first recorded it.
What performance does PopulaceLab (test) show?
Server fps averaged 236 over the last 48 hours, with a floor of 167. Entity count reached 130,693, covering buildings, deployables and the rest of the world. Memory use reached 6,988 MB at peak. Lag, for players, means low fps alongside a growing entity count.
Tags
What do PopulaceLab (test)'s tags stand for?
Tags from PopulaceLab (test), as read by the game's server browser, are: gmvanilla (Game mode): The vanilla survival format; mp3 (Max players): Player slots: 3; ts8 (Group limit): Default team size of 8; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^z (Modded): Modded listing, where plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
On Rust Server Analytics, which lists and filters feature PopulaceLab (test)?
Among the Rust Server Analytics lists PopulaceLab (test) fits are: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Player numbers
Against other Rust servers, how does PopulaceLab (test) compare?
Player hours for the last seven days place PopulaceLab (test) at #14,898, in the top 67% of the ranked field.
How many players does PopulaceLab (test) carry?
PopulaceLab (test) is offline at this refresh; the last contact was 14 hours ago. Averaging 0 players across seven days, the server reached a peak of 1. The 48-hour peak window is 22:00 UTC, at an average of 0 players.
Settings
How is PopulaceLab (test) configured, and what rules apply?
The name of PopulaceLab (test) does not state a gather rate. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. Carbon plugins are run. Anti-cheat status: VAC on.
What is the map for PopulaceLab (test)?
A procedural map of size 4,500 with seed 1530458240, generated by the game, runs on PopulaceLab (test). The map is reproducible from its size and seed and can be seen on RustMaps from here. The name of the map is Custom Map.
How to join
How can a player join PopulaceLab (test)?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 24.8.85.119:28335.