At press time 11,721 servers48,587 players110 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 14,840

PopulaceLab (test)

Offline 24.8.85.119:28335 checked 19h ago

PopulaceLab (test) is a Rust server. It was offline at the last count; over the past week it averaged 0, with a peak of 1. It stands at No. 14,840 of the ranked servers, the top 67%. It last wiped 2d ago. Its own tags class it as modded, carbon.

§ 1Attendance

AveragePeak
0123401:0006:0012:0017:0023:0004:00

Hourly average and peak, UTC.

§ 2Performance

010020030040001:0006:0012:0017:0023:0004:00

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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
15k10k15k20k17 Oct19 Oct21 Oct24 Oct26 Oct28 Oct

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

§ 4The wipe scheduleno rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

The rhythm
Usual gap4.5 days

between real wipes

On rhythm0%

of its recent wipes

Wipe-day peak1

players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctSat 24 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 20:37 UTC2d ago 1 – running 0
Sat 24 Oct, 21:38 UTC4d 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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 ShockRust | Blue | NoLimit46/500 no group limit · 156 on average
  2. 2 МИНИ-КАРТА 2Х | STORM | FPS+ 28.10127/100 EU · groups of 8+ · weekly · 128 on average
  3. 3 RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.1044/225 EU · groups of 16+ · weekly · 117 on average
  4. 4 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.1042/700 EU · groups of 16+ · monthly · 92 on average
  5. 5 RustSpain.com | EU Main7/200 EU · groups of 12+ · weekly · 88 on average
  6. 6 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.105/1000 EU · groups of 16+ · monthly · 84 on average

§ 7Questions answeredfrom the figures in this entry

Server details

On which Rust version does PopulaceLab (test) operate?

The server PopulaceLab (test) is on Rust network protocol 2635 and build 168909, hosted on Windows. The protocol must match on your game to join; the update comes through Steam.

What does uptime look like on PopulaceLab (test), and is it up?

Offline at present: PopulaceLab (test), last seen 19 hours ago. A restart came about 31 hours ago, by the server's own uptime figure. In the last 7 full days it was up for 30 of 168 hours, 18% of the time. The first sighting at Rust Server Stats was on 17 October 2026.

What is the performance of PopulaceLab (test) like?

The records show an average of 237 server fps over 48 hours, never below 167. Of note: 130,693 entities at the peak, counting buildings, deployables and the rest. Of note: memory use reached 6,988 MB. What players feel as lag: fps running low and entities climbing.

Where does PopulaceLab (test) operate from?

The server publishes no region: PopulaceLab (test). The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. At 24.8.85.119:28335 stands the address.

Settings and map

The map for PopulaceLab (test): which one is it?

PopulaceLab (test) runs a procedural map, generated by the game, of size 4,500 with seed 1530458240. The map repeats with the same size and seed; this page links to it on RustMaps. Map name, as listed: Custom Map.

What settings and rules does PopulaceLab (test) run?

Nothing in the name of PopulaceLab (test) gives a gather rate. Groups are capped at 8 players, the standard default. Play is survival, gather, build and raid: the standard game. Combat and raiding between players are permitted. Plugins or settings change the game; it appears under Modded in the browser. Carbon plugins are in use. The VAC anti-cheat from Valve is active.

Population

How full does PopulaceLab (test) get?

No answer from PopulaceLab (test) at the latest refresh; it was last seen 19 hours ago. Over seven days the mean is 0 players, with a peak of 1.

Against other Rust servers, how is PopulaceLab (test) ranked?

Ranked by player hours over the last seven days, PopulaceLab (test) stands at #14,840, in the top 67% overall.

Tags, lists

Where does PopulaceLab (test) appear among the Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include PopulaceLab (test): Modded Rust servers. On the server list it comes up under these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

The tags on PopulaceLab (test): what do they signify?

The game's server browser reads the tags PopulaceLab (test) publishes: gmvanilla (Game mode): The vanilla survival mode; mp3 (Max players): 3 is the number of slots; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): Protocol 2635: joining needs the same game version; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^z (Modded): Under Modded, because settings or plugins alter the game; ^y (Carbon): Carbon, a framework for plugins, runs here. At the top of this page are its current players, queue and world creation time, all taken from the tags.

The wipes

What is the shape of wipe day on PopulaceLab (test)?

The average peak across recent wipes was 1 players. 2 hours after the latest wipe, the crowd peaked.

When does PopulaceLab (test) wipe?

Wipes on PopulaceLab (test) follow no fixed times, so no next wipe is forecast. The monthly force wipe falls on every Rust server alike, and Thursday 5 November at 19:00 UTC is the next one. The world now in play was generated 2 days 3 hours ago.

Joining the server

How does one connect to PopulaceLab (test)?

To connect, open the console with F1 in Rust and enter client.connect 24.8.85.119:28335. The Launch Rust and join button on this page does the same through Steam.

§ 8Key to the tagswhat each one means

Published as mp3,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y

Game

gmvanilla
Game mode The vanilla survival mode.
mp3
Max players 3 is the number of slots.
ts8
Group limit Set at the game default of 8 per team.
v2635
Protocol Protocol 2635: joining needs the same game version.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^z
Modded Under Modded, because settings or plugins alter the game.
^y
Carbon Carbon, a framework for plugins, runs here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.