PopulaceLab (test)
Online 24.8.85.119:28335 checked 7m ago
Measurements
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
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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 wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
| 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.
Quick answers
Population
How does PopulaceLab (test) rank against other Rust servers?
Over the past week it ranks #14,862 for player hours, which puts PopulaceLab (test) in the top 67% of all ranked servers.
How busy is PopulaceLab (test)?
Of its 3 slots, PopulaceLab (test) is using 0 right now. Seven days of counting give an average of 0 players and a peak of 1. In the last 48 hours the peak hour came at 22:00 UTC, averaging 0 players.
Tags
What do the server tags on PopulaceLab (test) mean?
These are the tags PopulaceLab (test) publishes, as read by the game's server browser: gmvanilla (Game mode): This is vanilla survival; mp3 (Max players): 3 slots are available; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): The plugin framework Carbon runs on this server. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include PopulaceLab (test)?
PopulaceLab (test) appears among the Rust Population lists that follow: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days and it will show up.
Wipe notes
What does wipe day look like on PopulaceLab (test)?
The busiest point of its recent wipes averaged 0 players. Peak came 0 hours into the latest wipe.
What is the wipe schedule on PopulaceLab (test)?
Irregular times are when PopulaceLab (test) wipes, which leaves no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 25 hours ago, that is how long the current world has stood.
Map and rules
Which map does PopulaceLab (test) run?
PopulaceLab (test) uses a map the game generates, procedural, at size 4,500 with seed 1530458240. You can look at it on RustMaps from this page: size and seed determine the map. You will see the map named Custom Map.
What are the rules and settings on PopulaceLab (test)?
The name tells you nothing about gather rates: PopulaceLab (test) states none. Eight players per group is the default, and it applies here. survival is what it runs, gather, build and raid, as in the standard game. Combat between players, raids included, is permitted. Modded is its browser category: plugins or settings change the game. You will find Carbon running as plugins. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does PopulaceLab (test) run?
The setup is Rust network protocol 2635 and build 168909 on Windows for PopulaceLab (test). Your game needs the same protocol to join; Steam takes care of updating it.
Does PopulaceLab (test) run smoothly?
In the last 48 hours, it averaged 241 server fps, with a low of 218. The entity count reached 130,693: buildings, deployables and all other objects. The highest memory usage was 6,521 MB. Lag, as players feel it, is low fps combined with a climbing entity count.
Is PopulaceLab (test) online, and how reliable is it?
You will find PopulaceLab (test) online now. Judging by the uptime it reports, the last restart was about 24 hours ago. Over the last 7 full days, 6 of 168 hours were online, or 4%. The first sighting by Rust Population was on 17 October 2026.
Where is PopulaceLab (test) located?
Nothing published by PopulaceLab (test) states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 24.8.85.119:28335.
How to join
How do I join PopulaceLab (test)?
Either enter client.connect 24.8.85.119:28335 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.