Station XX-14840 · no signal
PopulaceLab (test)
Offline 24.8.85.119:28335 checked 18h ago
- Players now
- 0/ 3
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #14,840
- top 67%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 3 slots
- Motion · 24 h
- M0.0■steady+0 players
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.
- usual gap
- 4.5 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 20:37 UTC2d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sat 24 Oct, 21:38 UTC4d ago | M0.0■steady | 0 | – | 2 days | 0 | |
| Sat 17 Oct, 18:27 UTC11d ago | M0.0▲rising | 1 | – | 7.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on PopulaceLab (test)?
Generated by the game, the map on PopulaceLab (test) is procedural, size 4,500 with seed 1530458240. Size and seed produce the same map, so RustMaps can show it from this page. Its map carries the name Custom Map.
Which settings and rules apply on PopulaceLab (test)?
No gather rate appears in the name of PopulaceLab (test). Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on PopulaceLab (test)?
PopulaceLab (test) is not responding at this moment and is offline, last seen 18 hours ago. Across seven days this server recorded an average of 0 players and a peak of 1.
How does PopulaceLab (test) rank against other Rust servers?
Over the last seven days, PopulaceLab (test) recorded enough player hours to reach #14,840 worldwide, placing it in the top 67% of all ranked servers.
Server details
How reliably does PopulaceLab (test) stay online?
As recorded now, PopulaceLab (test) is not reachable, the last contact having been 18 hours ago. Going by the uptime figure it reports, it restarted about 31 hours ago. Of the 168 hours in the last 7 full days, it was up for 30, or 18% of the time. 17 October 2026 is when Rust Server Trends first recorded it.
How well does PopulaceLab (test) perform under load?
Its average server fps over the last 48 hours was 235, and it never dropped below 167. At its highest, it carried 130,693 entities: buildings, deployables and the world's other contents. Memory use peaked at 6,988 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Where in the world is PopulaceLab (test) hosted?
No region is published by PopulaceLab (test). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 24.8.85.119:28335.
What build of Rust does PopulaceLab (test) use?
PopulaceLab (test) is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on PopulaceLab (test)?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 2 hours after the wipe.
How often does PopulaceLab (test) wipe, and on which days?
There is no next wipe to predict at PopulaceLab (test), since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 2 days 2 hours is how long the current world has been running.
Lists and tags
What do the server tags on PopulaceLab (test) mean?
The game's server browser reads the tags PopulaceLab (test) publishes: gmvanilla (Game mode): You'll find vanilla survival here; mp3 (Max players): Slots: 3; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does PopulaceLab (test) appear?
You will find PopulaceLab (test) on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under 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.
Join the server
How do you connect to PopulaceLab (test)?
You can connect by pressing F1 in Rust and typing client.connect 24.8.85.119:28335 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.