PopulaceLab (test)
Offline 24.8.85.119:28335 checked 15h ago
Server instruments
last reading Wed 04:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 167 · below 20 is lag, below 10 is badEntities
48 h range 121,373–130,693 · memory 6,988 MBUptime
1 days 7 hours since its last restart, at the last readingPlayers
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 UTC11d 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- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on PopulaceLab (test)?
The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.
When does PopulaceLab (test) wipe?
There is no next wipe to predict: PopulaceLab (test) wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 46 hours ago.
Tag meanings
Which tags does PopulaceLab (test) carry, and what do they mean?
These are the tags PopulaceLab (test) publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show PopulaceLab (test)?
On Rust Metrics, PopulaceLab (test) sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Population
What position does PopulaceLab (test) hold among Rust servers?
Player hours over seven days put PopulaceLab (test) at #14,845, in the top 67% of all ranked servers.
What player count does PopulaceLab (test) carry?
Reading for PopulaceLab (test): offline at this moment; last seen 15 hours ago. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 22:00 UTC, averaging 0 players at that hour.
Server details
What location is PopulaceLab (test) hosted in?
No region comes from PopulaceLab (test). Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 24.8.85.119:28335.
What Rust version is PopulaceLab (test) on?
Rust network protocol 2635 and build 168909 on Windows is the build PopulaceLab (test) runs. To get in, your game needs the same protocol; Steam applies the update.
How does PopulaceLab (test) perform?
Reading: 236 server fps on average across the last 48 hours. It never dropped below 167. Peak entity count: 130,693. Buildings, deployables and all else included. Check: memory. Peak use was 6,988 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on PopulaceLab (test), and is it online?
Reading: offline. PopulaceLab (test) last answered 15 hours ago. By its reported uptime, the last restart was roughly 31 hours ago. Uptime for the last 7 full days: 30 of 168 hours, or 18%. Reading: first seen 17 October 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on PopulaceLab (test)?
Reading the name gives no gather rate for PopulaceLab (test). 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.
Which map is live on PopulaceLab (test)?
Check: map. Procedural, size 4,500, seed 1530458240, generated by the game on PopulaceLab (test). Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.
How to join
What do you do to join PopulaceLab (test)?
Check: join. Open Rust, press F1, then enter client.connect 24.8.85.119:28335. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.