Rust Data

rustdata.spaceservers24.8.85.119:28337.ipynb

Run all rust-data · live

‹ All servers

Offline 24.8.85.119:28335 checked 9h ago

PopulaceLab (test)

moddedcarbon

Connect

srv = rust.server("24.8.85.119:28337")
print(srv.connect_command)

Right now

srv.summary()
players now 0/3 # 0% full
7-day average 0 # peak 1
rank #14,899 # top 67%
last wipe 1d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75120:0002:0009:0015:0022:0004:00Wiped Mon 26 Oct, 20:37 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040020:0002:0009:0015:0022:0004: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 · daily · 1 is best

srv.rank.plot(invert=True)  # 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

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 20:37 UTC1d ago NaN NaN running 0
1 Sat 24 Oct, 21:38 UTC3d ago 0 NaN 2 days 0
2 Sat 17 Oct, 18:27 UTC10d ago 1 NaN 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.

display(srv.map, srv.info())

Map

4500 · seed 1530458240
Custom map, no picture published
map
Custom Map
size
4500
seed
1530458240

Server

srv.info()
address
24.8.85.119:28335
region
–
max players
3
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 20:37 UTC
hostname
–
first seen
17 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 156 on average194/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average129/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average181/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average136/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average18/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does PopulaceLab (test) rank?

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

How full does PopulaceLab (test) run?

PopulaceLab (test) returns no live count at this refresh, having last been seen 9 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 22:00 UTC is the busiest, at 0 players.

Server facts

How well does PopulaceLab (test) perform?

Server fps over the last 48 hours averages 236; the floor is 167. The entity count peaked at 130,693, covering buildings, deployables and the rest of the world. Memory peaked at 6,988 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on PopulaceLab (test)?

The build is Rust network protocol 2635 and build 168909 on Windows, run by PopulaceLab (test). The protocol has to match before you can join, and Steam does the updating.

How reliable is PopulaceLab (test), and is it up?

The latest sample has PopulaceLab (test) offline, with a last sighting 9 hours ago. Count back 31 hours from its reported uptime to get the last restart. 30 of 168 hours up over the last 7 full days, or 18%. Rust Data logged it first on 17 October 2026.

In which location is PopulaceLab (test) hosted?

No region is published by PopulaceLab (test). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 24.8.85.119:28335 is its address.

Settings and map

Which rules apply on PopulaceLab (test), and what settings?

No gather rate appears in the name: PopulaceLab (test). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has PopulaceLab (test) loaded?

PopulaceLab (test) runs a procedural map of size 4,500 with seed 1530458240, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Recorded under map name: Custom Map.

Wipe data

When does PopulaceLab (test) wipe, and on what schedule?

No next wipe can be predicted for PopulaceLab (test), which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 41 hours ago, and that is the one in play.

What is wipe day on PopulaceLab (test) like?

The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

Where does PopulaceLab (test) appear among Rust Data lists and filters?

The Rust Data lists that PopulaceLab (test) fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

How should you read the server tags on PopulaceLab (test)?

The game's server browser reads these tags from PopulaceLab (test): gmvanilla (Game mode): Game mode: vanilla survival; mp3 (Max players): Slot count: 3; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way to join PopulaceLab (test)?

The manual route: launch Rust, F1, then client.connect 24.8.85.119:28335. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp3
Max players Slot count: 3.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon The plugin framework in use is 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.

Rust Data 76,398 players 11,761 servers online