DWG RG-S14862Server sheetchecked 8m ago
PopulaceLab (test)
Online 24.8.85.119:28335 checked 8m 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.
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 |
|---|---|---|---|---|
| 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
Quick answers
Server details
What uptime is recorded for PopulaceLab (test), and is it up?
PopulaceLab (test) is up at this moment. Counted from its reported uptime, the last restart was about 24 hours ago. 6 of 168 hours up over the last 7 full days, which is 4% of the time. The first sighting of it by Rust Graphs was on 17 October 2026.
Is PopulaceLab (test) stable in the figures recorded?
241 server fps on average over the last 48 hours, and never under 218. Counted at its highest: 130,693 entities, buildings, deployables and the rest of the world included. Memory use peaked at 6,521 MB. Players feel low fps and a climbing entity count as lag.
What location is recorded for PopulaceLab (test)?
There is no region published by PopulaceLab (test). No lookup of the machine's location is done: Rust Graphs shows where a server says it is. You will find it at 24.8.85.119:28335.
What Rust version is recorded for PopulaceLab (test)?
Rust network protocol 2635 and build 168909 on Windows: that is what PopulaceLab (test) runs. Steam updates your game, which must be on the same protocol for you to join.
Population
What does the population history show for PopulaceLab (test)?
0 of 3 slots on PopulaceLab (test) are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 1. The 48-hour peak falls at 22:00 UTC, averaging 0 players.
In the rankings, which position does PopulaceLab (test) hold?
Player hours over seven days place PopulaceLab (test) at #14,862, within the top 67% of ranked servers.
Wipe times
On PopulaceLab (test), what does the data show for wipe day?
At their busiest, its recent wipes drew 0 players on average. At 0 hours after the latest wipe the crowd was at its peak.
What wipe schedule has been recorded for PopulaceLab (test)?
There is no next wipe to predict at PopulaceLab (test), which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 25 hours ago.
Rules and settings
Which settings does PopulaceLab (test) run, and what rules?
The name of PopulaceLab (test) records no gather rate. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Carbon. VAC is on: that is Valve's anti-cheat.
Which map has PopulaceLab (test) loaded?
PopulaceLab (test) runs a procedural map of size 4,500 with seed 1530458240, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.
Filters
On Rust Graphs, which lists and filters contain PopulaceLab (test)?
The Rust Graphs lists that carry PopulaceLab (test) are: Modded Rust servers. It is returned by these filters 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 meaning is attached to each tag on PopulaceLab (test)?
Tags published by PopulaceLab (test), and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp3 (Max players): 3 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
How to join
By what method do you join PopulaceLab (test)?
Connect with client.connect 24.8.85.119:28335: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
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.