PPL14885=
PopulaceLab (test)
Online 24.8.85.119:28335 checked 13m 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
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 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.
-
01MODPlayers 40/500
-
02MODPlayers 125/100
-
03MODPlayers 48/225
-
04MODPlayers 18/700
-
05MODPlayers 6/200
-
06MODPlayers 7/1000
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show PopulaceLab (test)?
On Rust Tracker, PopulaceLab (test) sits in these lists: Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Which tags does PopulaceLab (test) carry, and what do they mean?
These tags are published by PopulaceLab (test) for the game's server browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp3 (Max players): Slots: 3; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^z (Modded): Under Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon is installed — a plugin framework. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
What should you expect on PopulaceLab (test) when wipe day lands?
The average peak across recent wipes: 0 players. The peak on the latest wipe came 0 hours after it.
On what schedule does PopulaceLab (test) wipe?
Wipe times at PopulaceLab (test) are irregular, so no next wipe can be predicted. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 30 hours.
Server Details
How reliable is PopulaceLab (test), and is it online now?
Tracking shows PopulaceLab (test) online as of now. About 29 hours ago it restarted last, based on reported uptime. 18% uptime over the last 7 full days, with 30 of 168 hours up. Rust Tracker logged it first on 17 October 2026.
Which Rust version is confirmed on PopulaceLab (test)?
Confirmed for PopulaceLab (test): Rust network protocol 2635 and build 168909, Windows. To join, your game must be on the same protocol; Steam handles the update.
Is PopulaceLab (test) holding performance?
Average server fps over the last 48 hours: 236, with a low of 167. Maximum entities carried: 130,693, from buildings and deployables to everything else. Peak memory use: 6,916 MB. Lag, as players experience it, comes from low fps and a rising entity count.
What location is PopulaceLab (test) hosted in?
Region: none published by PopulaceLab (test). The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 24.8.85.119:28335.
Player Count
Is PopulaceLab (test) busy?
Slots 3; players on board 0: that is PopulaceLab (test) now. Peak of 1 in the last seven days, average 0 players. At 22:00 UTC it drew its highest average of the last 48 hours: 0 players.
Where does PopulaceLab (test) sit in the server rankings?
Top 67% of all ranked servers, and #14,885 on seven-day player hours: PopulaceLab (test).
Settings
Which settings and rules are confirmed on PopulaceLab (test)?
No gather rate appears in PopulaceLab (test)'s name. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Players can raid and fight each other here. The server browser lists it under Modded, where plugins or settings change the game. Carbon plugins run on it. On: VAC, Valve's anti-cheat.
Which map is confirmed for PopulaceLab (test)?
The map on PopulaceLab (test) is procedural, size 4,500, seed 1530458240, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Custom Map.
Connect
Which steps join PopulaceLab (test)?
To connect: start Rust, press F1, enter client.connect 24.8.85.119:28335 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
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.