Skip to the coverage
Live Rust server stats, updated every five minutes.
Rust Live Stats
Live
37,516 players on Rust servers right now 11,644 servers online 2,896 with players on 66 fresh wipes in the last three hours PopulaceLab (test): 0 players on now Updated every five minutes

LiveLive coverage · Rust server

PopulaceLab (test)

Key points

  • 0 of 3 players are on now, 0% full.
  • Over the last seven days it averages 0 players, with a peak of 1.
  • It ranks #14,885, the top 67% of all ranked servers.
  • The current map has been up 1d 6h, since Monday 26 October, 20:37 UTC.
Join
moddedcarbon

Live coverage

newest first · every post is a reading of this server

Now: 0 of 3 players

0/ 3players now 0% full
07-day averagepeak 1
#14,885ranktop 67%
1d agolast wipeno schedule published
–next wipeno rhythm it keeps

Players on PopulaceLab (test)

Players

AveragePeakWipe
00.250.50.75120:0002:0008:0013:0019:0001:00Wiped Mon 26 Oct, 20:37 UTCWIPE

Hourly average and peak, UTC.

How the server is running

Server performance

Server fpsWipe
010020030040020:0002:0008:0013:0019:0001: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.

Rank #14,885 today

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.

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.

4.5 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
0wipe-day peakplayers, 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.

Wipes

newest first

Wipe: no peak counted yet

Peak
–
Crowd
–
Lasted
running
Players before
0

Wipe peaks at 0 players

Peak
0
Crowd
–
Lasted
2 days
Players before
0

Wipe peaks at 1 player

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
no group limit · 160 on average
39 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10
EU · groups of 8+ · weekly · 128 on average
123 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 114 on average
46 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 88 on average
17 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
7 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 83 on average
7 / 1000

Quick answers

from the figures on this page

Wiping

What should you expect from wipe day on PopulaceLab (test)?

The average peak across its recent wipes is 0 players. The crowd on the latest wipe peaked 0 hours in.

On what timetable does PopulaceLab (test) wipe?

PopulaceLab (test) wipes with no fixed pattern, so there is nothing to predict. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 30 hours.

Lists and tags

Where does PopulaceLab (test) appear in Rust Live Stats lists and filters?

On Rust Live Stats, PopulaceLab (test) is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days it appears on the server list.

What meaning do the tags on PopulaceLab (test) carry?

These are the tags PopulaceLab (test) makes public: gmvanilla (Game mode): Survival in the vanilla style; mp3 (Max players): Slots: 3; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^z (Modded): Modded: plugins or changed settings alter the game; ^y (Carbon): It uses the plugin framework Carbon. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.

Player numbers

How full is PopulaceLab (test) at the moment?

PopulaceLab (test) is carrying 0 players at the moment, with 3 slots in total. Peak over the past week: 1. Average: 0 players. Between now and 48 hours back, 22:00 UTC drew the most players, 0 on average.

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

Player hours over seven days put PopulaceLab (test) at #14,885, in the top 67% of all ranked servers.

Map and rules

What settings and rules does PopulaceLab (test) run?

The name PopulaceLab (test) carries no gather rate. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. The plugin load is Carbon. VAC is enabled: Valve's anti-cheat.

Can you tell me the map for PopulaceLab (test)?

A procedural map of 4,500 with seed 1530458240, generated by the game, runs on PopulaceLab (test). RustMaps shows it from this page, since equal size and seed give an equal map. Map name, as listed: Custom Map.

About the server

Which region is PopulaceLab (test) hosted in?

No region is published by PopulaceLab (test). The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 24.8.85.119:28335 is its address.

How well does PopulaceLab (test) perform?

The average server fps was 239 over the last 48 hours; the lowest was 174. It supported up to 130,693 entities, covering buildings, deployables and all other objects. Up to 6,916 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.

What version of Rust is running on PopulaceLab (test)?

PopulaceLab (test) operates on Windows with Rust network protocol 2635 and build 168909. To join, your game must use the same protocol; Steam handles the update for you.

How reliable is PopulaceLab (test), and is it online at the moment?

Right now PopulaceLab (test) is online. The uptime it reports puts the last restart at about 28 hours ago. 30 of 168 hours were online in the last 7 full days, giving 18% uptime. Rust Live Stats has tracked it since 17 October 2026.

Connecting

What steps connect you to PopulaceLab (test)?

Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 24.8.85.119:28335.

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival in the vanilla style.
mp3
Max players Slots: 3.
ts8
Group limit Teams stop at 8, the default the game ships with.
v2635
Protocol You need protocol 2635 on your game to get in.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the standard the game uses.
$r?
Region code No region code is set here.

Mods and access

^z
Modded Modded: plugins or changed settings alter the game.
^y
Carbon It uses the plugin framework Carbon.

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.