PopulaceLab (test)
Offline 24.8.85.119:28335 checked 31m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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.
Wipes
every wipe as a delivery, newest first-
Mon 26 Oct, 20:37 UTC 20:37 UK · 1d agoWipe delivered
- Peak
- –
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Sat 24 Oct, 21:38 UTC 22:38 UK · 3d agoWipe delivered
- Peak
- 0
- Crowd
- –
- Lasted
- 2 days
- Players before
- 0
-
Sat 17 Oct, 18:27 UTC 19:27 UK · 10d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- 7.1 days
- Players before
- 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.
- ShockRust | Blue | NoLimit 50 / 500
- МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 134 / 100
- RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 53 / 225
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 28 / 700
- RustSpain.com | EU Main 4 / 200
- 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 9 / 1000
Quick answers
From the figures on this page.
Player activity
How does PopulaceLab (test) compare with other Rust servers in the rankings?
Over the past seven days, PopulaceLab (test) has climbed to #14,902 for player hours, putting it in the top 67% of all ranked servers.
How many players are on PopulaceLab (test) right now?
At the moment PopulaceLab (test) is offline, having last been seen 31 minutes ago. The seven-day figures show an average of 0 players and a peak of 1. The busiest hour over the last 48 hours was 22:00 UTC, averaging 0 players.
Map and rules
On what map does PopulaceLab (test) take place?
The game generates the procedural map on PopulaceLab (test) at size 4,500 with seed 1530458240. Size and seed match means the map matches, so you can view it on RustMaps from this page. Its name for the map: Custom Map.
What are the rules on PopulaceLab (test), and what settings does it run?
You will not find a gather rate in the name of PopulaceLab (test). Up to 8 players can join a group, the default for the game. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. Plugins or settings alter the game on this one, which sits under Modded in the server browser. Plugins come from Carbon. The VAC anti-cheat from Valve is enabled.
Server details
In which region is PopulaceLab (test) based?
No region is published by PopulaceLab (test). Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 24.8.85.119:28335.
What is the performance like on PopulaceLab (test)?
Averaged over the last 48 hours, server fps was 236, with a low of 167. Buildings, deployables and all the rest of the world pushed its entity count as high as 130,693. Memory use peaked at 6,916 MB. Lag, to players, means low fps alongside an entity count on the rise.
Is PopulaceLab (test) up, and how good is its uptime?
PopulaceLab (test) is offline at the moment, with the last sighting 31 minutes ago. Its reported uptime suggests a restart roughly 30 hours ago. It was up 30 of 168 hours over the last 7 full days, 18% of the time. It was first seen by Rust Wipe Tracker on 17 October 2026.
What Rust version is PopulaceLab (test) using?
On Windows, PopulaceLab (test) runs Rust network protocol 2635 and build 168909. The same protocol is required to join, and Steam takes care of updating it.
Wipe times
What happens on PopulaceLab (test) when wipe day arrives?
The average busiest point of its recent wipes was 0 players. On the latest wipe, 0 hours passed before the crowd peaked.
On what schedule does PopulaceLab (test) reset its map?
PopulaceLab (test) wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. The world it is running was made 32 hours.
Tags and listings
Where does PopulaceLab (test) appear across the Rust Wipe Tracker lists and filters?
These Rust Wipe Tracker lists take PopulaceLab (test): Modded Rust servers. On the server list, apply Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days and it appears.
How should you read the tags on PopulaceLab (test)?
gmvanilla (Game mode): Vanilla survival gameplay; mp3 (Max players): It holds 3 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): The plugin framework here is Carbon are the tags PopulaceLab (test) publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
How to join
What steps do you take to join PopulaceLab (test)?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 24.8.85.119:28335.