PopulaceLab (test)
Offline 24.8.85.119:28335 checked 5h ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on PopulaceLab (test)?
At their busiest, its recent wipes averaged 0 players. The crowd on the latest wipe reached its peak 0 hours in.
What is the wipe schedule on PopulaceLab (test)?
No next wipe can be predicted: PopulaceLab (test) wipes when it chooses, at irregular times. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 37 hours ago the server made the world it is on now.
Player counts
How busy is PopulaceLab (test)?
The last time PopulaceLab (test) was seen was 5 hours ago, and it is offline now. A seven-day average of 0 players, with a peak of 1. Its busiest point in the last 48 hours was 22:00 UTC, averaging 0 players.
How does PopulaceLab (test) rank against other Rust servers?
Ranked #14,867 on seven-day player hours, PopulaceLab (test) is in the top 67% of all ranked servers.
Settings and rules
Which map does PopulaceLab (test) run?
The map on PopulaceLab (test) is procedural, size 4,500 with seed 1530458240, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map. The map is called Custom Map.
What are the rules and settings on PopulaceLab (test)?
No gather rate appears in the name PopulaceLab (test). Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
About the server
Which version of Rust does PopulaceLab (test) run?
The build on PopulaceLab (test) is Rust network protocol 2635 and build 168909, running on Windows. Steam updates your game for you, and the protocol has to match for you to join.
Is PopulaceLab (test) online, and how reliable is it?
PopulaceLab (test) is down just now; the last sighting was 5 hours ago. The uptime it reports puts the last restart at about 31 hours ago. It was up 30 of 168 hours across the last 7 full days, or 18% of the time. The first record of it on Rust Heatmap is 17 October 2026.
Where is PopulaceLab (test) located?
Nothing about a region comes from PopulaceLab (test). What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 24.8.85.119:28335.
Does PopulaceLab (test) run smoothly?
Average server fps over the last 48 hours was 236; it never dropped below 167. The world held as many as 130,693 entities, buildings and deployables included. Memory use reached 6,988 MB at most. Lag, as players experience it, comes from low fps and a rising entity count.
Lists and filters
Which Rust Heatmap lists and filters include PopulaceLab (test)?
The Rust Heatmap lists that PopulaceLab (test) fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
What do the server tags on PopulaceLab (test) mean?
The game's server browser reads the tags PopulaceLab (test) publishes: gmvanilla (Game mode): Survival in vanilla form; mp3 (Max players): This server has 3 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): Carbon provides the plugin framework here. The top of this page also shows the tags for players now, the queue and when the world was made.
Connect
How do I join PopulaceLab (test)?
Enter client.connect 24.8.85.119:28335 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you.