Local forecast
PopulaceLab (test)
Online 24.8.85.119:28335 checked 11m ago
Current conditions
observed 11m agoplayers now
0% full
- 7-day average
- 0
- peak 1
- Rank
- #14,862
- top 67%
- Last wipe
- 1d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
Next wipe
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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.
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.
Past weather: its wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 26 Oct, 20:37 UKMon 26 Oct, 20:37 UTC · 1d ago | – | – | running | 0 |
| Sat 24 Oct, 22:38 UKSat 24 Oct, 21:38 UTC · 3d ago | 0 | – | 2 days | 0 |
| Sat 17 Oct, 19:27 UKSat 17 Oct, 18:27 UTC · 10d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer details
Does PopulaceLab (test) hold a steady performance?
Its average over the last 48 hours was 241 server fps, and it never dropped below 218. The world held as many as 130,693 entities, buildings and deployables included. The peak memory draw was 6,521 MB. Lag is what players call it when fps is low and entities are piling up.
How reliable is PopulaceLab (test), and is it online now?
Right now PopulaceLab (test) is up and running. The uptime it reports puts the last restart about 24 hours ago. It was up for 6 of 168 hours across the last 7 full days, 4% of the time. On 17 October 2026 it was first recorded by Rust Wipe Stats.
What location is PopulaceLab (test) based in?
For PopulaceLab (test), no region is published. The location Rust Wipe Stats shows is the one the server claims; the machine's real position is not looked up. You can reach it at 24.8.85.119:28335.
What Rust version is PopulaceLab (test) on?
Rust network protocol 2635 and build 168909 on Windows is what PopulaceLab (test) runs. Steam updates your game for you; the protocol must match to join.
Tags, lists and filters
Which meaning sits behind each tag on PopulaceLab (test)?
For the game's server browser, PopulaceLab (test) publishes these tags: gmvanilla (Game mode): This is vanilla survival; mp3 (Max players): 3 player slots are available; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909 is installed here; ptrak (Networking): RakNet is the network layer, as standard for the game; $r? (Region code): The region field is left blank; ^z (Modded): Modded is its category, with plugins or settings changing the game; ^y (Carbon): Plugins run through Carbon here. The tags also carry the current players, the queue and when the world was created; you will find them at the top of this page.
Where does PopulaceLab (test) appear among the Rust Wipe Stats lists and filters?
PopulaceLab (test) appears in the following Rust Wipe Stats lists: Modded Rust servers. These filters on the server list will bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Map and rules
What map is PopulaceLab (test) on?
The game generates the map on PopulaceLab (test), procedural, size 4,500, seed 1530458240. You can look at it on RustMaps from this page: same size and seed, same map. The map goes by Custom Map.
What settings does PopulaceLab (test) use, and what rules does it enforce?
Gather rate is not given in the name for PopulaceLab (test). No group setting is published, so the game default of 8 players applies. survival is the game mode, gathering, building and raiding, as the game normally plays. Both PvP and raiding are on. You will find it under Modded, with plugins or settings changing the game. Carbon are the plugin frameworks it runs. This server has VAC switched on.
Wipe days
Which days and times does PopulaceLab (test) schedule its wipes for?
There is no next wipe to predict, because PopulaceLab (test) wipes at irregular times. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. 26 hours is how long the current world has been running.
What happens on PopulaceLab (test) when wipe day arrives?
The average peak across its recent wipes was 0 players. Peak numbers on the latest wipe arrived 0 hours after the reset.
Player counts
Is PopulaceLab (test) busy or quiet?
The live count for PopulaceLab (test): 0 players, with 3 slots in total. Across the past week it peaked at 1 and averaged 0 players. At 22:00 UTC it was busiest over the past 48 hours, averaging 0 players.
How does PopulaceLab (test) compare with other Rust servers in the rankings?
Player hours over the past week put PopulaceLab (test) at #14,862, inside the top 67% of all ranked servers.
How to join
What do you do to join PopulaceLab (test)?
Enter client.connect 24.8.85.119:28335 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you.