Rust Data LabData lab · live
Live readings Servers11,755 Players61,286 Populated3,487 Fresh wipes · 3h126 Sampled every 5 min

Element card · group Modded · atomic number 14,867, its rank

PopulaceLab (test)

Online 24.8.85.119:28335 checked 11m ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 3 0% full Room to join
7-day average0peak 1
Rank · atomic number#14,867top 67%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeakWipe
00.250.50.75120:0001:0006:0011:0016:0021:00Wiped Mon 26 Oct, 20:37 UTCWIPE

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
Server fpsWipe
010020030040020:0001:0006:0011:0016:0021:00Wiped Mon 26 Oct, 20:37 UTCWIPE

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k17 Oct19 Oct21 Oct23 Oct25 Oct27 Oct

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

Reaction kinetics

Wipe schedule

no rhythm it keeps

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

usual gap4.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

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

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 76
    ShockRust | Blue | NoLimit no group limit · 163 on average 76/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 122
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 122/ 100
  3. 3 Re RETRO RUST #1 … 81
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 113 on average 81/ 225
  4. 4 Ru RustSpain.com … 31
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 31/ 200
  5. 5 Ru 404 RUST 2Х|ДЛ… 81
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average 81/ 700
  6. 6 Ru 404 RUST 2Х|ДЛ… 17
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 17/ 1,000

Quick answers

from the figures on this page

Settings and map

What map is in play on PopulaceLab (test)?

The map on PopulaceLab (test) is procedural at size 4,500 with seed 1530458240, made by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map. On the map name: Custom Map.

How is PopulaceLab (test) configured, and what rules apply?

The name of PopulaceLab (test) carries no gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Raids and player fights are part of play here. Plugins or settings change the game, so the browser lists it under Modded. Plugins in use: Carbon. Anti-cheat is on: Valve's VAC.

Server facts

In what location does PopulaceLab (test) sit?

No region is published by PopulaceLab (test). The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. 24.8.85.119:28335 is the address it uses.

Which Rust version is PopulaceLab (test) on?

On Windows, PopulaceLab (test) is running Rust network protocol 2635 and build 168909. Your game needs to match the protocol to join, and Steam updates it automatically.

Does PopulaceLab (test) stay up, and how reliable is its uptime?

PopulaceLab (test) is live as of now. According to the uptime it reports, the last restart was about 24 hours ago. For the last 7 full days, 6 of 168 hours were online, giving 4% uptime. It first appeared to Rust Data Lab on 17 October 2026.

How well does PopulaceLab (test) perform?

The last 48 hours show an average of 241 server fps and a minimum of 218. The entity count reached 130,693, including buildings, deployables and all other world items. Up to 6,521 MB of memory was used. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe schedule

How often does a wipe happen on PopulaceLab (test), and at what time?

There is no next wipe to predict for PopulaceLab (test), which wipes at irregular times. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 26 hours ago.

On PopulaceLab (test), what happens when wipe day arrives?

Recent wipes on average reached 0 players at their busiest. 0 hours after the latest wipe, the crowd peaked.

Where it appears

What should you understand from the tags PopulaceLab (test) carries?

gmvanilla (Game mode): This is vanilla survival; mp3 (Max players): It has 3 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; ^y (Carbon): This server uses the Carbon plugin framework: that is the tag list PopulaceLab (test) publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does PopulaceLab (test) come up?

You will find PopulaceLab (test) on the following Rust Data Lab lists: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Player counts

What position does PopulaceLab (test) hold among Rust servers?

PopulaceLab (test) sits at #14,867 for seven-day player hours, placing it in the top 67% of ranked servers.

How many players does PopulaceLab (test) have at the moment?

At the moment PopulaceLab (test) has 0 of its 3 slots filled. Averaged over the past week: 0 players, peaking at 1. Over 48 hours, the highest average fell at 22:00 UTC, at 0 players.

How to join

How can you connect to PopulaceLab (test)?

Open the console with F1 in Rust and type client.connect 24.8.85.119:28335. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

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

Game

gmvanilla
Game mode This is vanilla survival.
mp3
Max players It has 3 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded You will find it under Modded: the game is altered by plugins or settings.
^y
Carbon This server uses the Carbon plugin framework.

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.