Server profile
PopulaceLab (test)
Offline, with 0 of 3 players on; ranked #14,840 of every public Rust server, the top 67%. It last wiped 2d ago.
Offline 24.8.85.119:28335 checked 20h ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 67% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 20:37 UTC2d ago | 1 | – | running | 0 |
| Sat 24 Oct, 21:38 UTC4d ago | 0 | – | 2 days | 0 |
| Sat 17 Oct, 18:27 UTC11d ago | 1 | – | 7.1 days | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
What does PopulaceLab (test) look like once wipe day arrives?
Recent wipes peaked at 1 players on average. 2 hours into the latest wipe, the crowd on the server reached its peak.
When does PopulaceLab (test) wipe, and how often?
PopulaceLab (test) wipes at times that vary, so its next wipe cannot be predicted. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. 2 days 3 hours have passed since its current world was created.
Server
What does performance look like on PopulaceLab (test)?
Average server fps over the last 48 hours was 237, with a floor of 167. Buildings, deployables and the rest took the entity count as high as 130,693. Memory use peaked at 6,988 MB. A climbing entity count and low fps are what players experience as lag.
What Rust version is live on PopulaceLab (test)?
The Rust build is network protocol 2635 and build 168909, running on Windows, for PopulaceLab (test). You can only join if your game is on the same protocol; Steam handles that update.
How reliable is PopulaceLab (test), and is it up at the moment?
PopulaceLab (test) is offline at the moment; the last time it was seen was 20 hours ago. Going by the uptime figure it gives, its last restart was around 31 hours ago. It spent 30 of the last 7 full days' 168 hours up, 18% of the time. On 17 October 2026 is when Rust Insights first saw it.
What location is listed for PopulaceLab (test)?
No region is published by PopulaceLab (test). Rust Insights reports the location a server declares, not the physical place of the machine. 24.8.85.119:28335 is where it answers.
Tags
Which meanings sit behind the tags on PopulaceLab (test)?
The tags gmvanilla (Game mode): The mode is vanilla survival; mp3 (Max players): It holds 3 slots; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; ^y (Carbon): The plugin framework here is Carbon are what PopulaceLab (test) publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Where does PopulaceLab (test) turn up among the Rust Insights lists and filters?
The Rust Insights lists that carry PopulaceLab (test) are Modded Rust servers, explained. You will find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Population history
How many players are on PopulaceLab (test) right now?
PopulaceLab (test) was last seen 20 hours ago and is offline right now. Over the past week it peaked at 1 and averaged 0 players.
In the ranking of Rust servers, where does PopulaceLab (test) place?
Player hours over seven days put PopulaceLab (test) at #14,840, within the top 67% of the ranked field.
Map and rules
What are the settings and rules for PopulaceLab (test)?
No gather rate appears in the name of PopulaceLab (test). The default of 8 players per group is what applies here. survival is the game mode, the standard game: gather, build, raid. Players may raid and fight one another. It is a Modded entry: plugins or settings modify the game. Carbon is the plugin count it runs. Anti-cheat: VAC, from Valve, is on.
What is the map on PopulaceLab (test)?
PopulaceLab (test) runs a procedural map of size 4,500 with seed 1530458240, generated by the game. Size and seed give the same map each time, so this page lets you look at it on RustMaps. Its map carries the name Custom Map.
Join
What is the way to join PopulaceLab (test)?
Open the console with F1 in Rust and enter client.connect 24.8.85.119:28335. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you.