PopulaceLab (test)
Online 24.8.85.119:28335 checked 6m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
48 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
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 4.5 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 0players, last three wipes
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
26 OCT 2026Mon 26 Oct, 20:37 UTC1d ago |
– | – | running | 0 |
24 OCT 2026Sat 24 Oct, 21:38 UTC3d ago |
0 | – | 2 days | 0 |
17 OCT 2026Sat 17 Oct, 18:27 UTC10d 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.
Quick answers
From the figures on this page.
Rules and settings
What settings and rules does PopulaceLab (test) run?
No gather rate appears in the name PopulaceLab (test). The group limit is 8 players, the game's default. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Carbon. The server has VAC, Valve's anti-cheat, turned on.
What is the map on PopulaceLab (test)?
Size 4,500, seed 1530458240: the game generates the procedural map on PopulaceLab (test). You can view the map on RustMaps from this page, as the same size and seed give the same map. Filed under map name: Custom Map.
Lists and filters
Which lists and filters on Rust Server Index is PopulaceLab (test) filed under?
These lists on Rust Server Index take PopulaceLab (test): Modded Rust servers, filed by play style. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the tags listed for PopulaceLab (test)?
These are the tags PopulaceLab (test) publishes; the game's server browser reads this list: gmvanilla (Game mode): Survival in vanilla form; mp3 (Max players): The queue ceiling sits at 3; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): Build on file: 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): No region code has been set; ^z (Modded): This one is Modded, since plugins or settings change how it plays; ^y (Carbon): Carbon provides the plugin framework. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
What should you expect on PopulaceLab (test) when wipe day comes?
Its recent wipes averaged 0 players at peak. 0 hours into the latest wipe, the crowd reached its peak.
How often is PopulaceLab (test) wiped, and on what schedule?
PopulaceLab (test) wipes at times that follow no pattern, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 31 hours.
Player counts
How is PopulaceLab (test) ranked compared with the rest?
Filed under rankings: #14,902 for PopulaceLab (test) on seven-day player hours, top 67% overall.
Is PopulaceLab (test) quiet or crowded?
The live count for PopulaceLab (test) stands at 0 players, out of 3 slots. The seven-day average is 0 players; the peak reached 1. Over the last 48 hours, 22:00 UTC drew the highest average: 0 players.
Server details
Which Rust build is PopulaceLab (test) running?
Rust network protocol 2635 and build 168909, on Windows, is what PopulaceLab (test) runs. To join you need the same protocol; Steam handles the update.
Is PopulaceLab (test) reachable, and does it stay up?
Right now PopulaceLab (test) is up and running. Its reported uptime gives the last restart as roughly 29 hours ago. Of the last 7 full days, 30 of 168 hours were up, 18% of the time. On 17 October 2026 it was first seen by Rust Server Index.
How well does PopulaceLab (test) perform?
Averaged over the last 48 hours, server fps was 236, with a low of 167. Buildings, deployables and everything else in the world came to as many as 130,693 entities. The peak memory figure stood at 6,916 MB. Lag, to players, is low fps and an entity count that climbs.
Which region is PopulaceLab (test) in?
No region is published by PopulaceLab (test). Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 24.8.85.119:28335.
Connecting
What steps lead onto PopulaceLab (test)?
If you would rather use the console, press F1 in Rust and enter client.connect 24.8.85.119:28335. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp3,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
mp3
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^z
^y
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.