Rust Server TrendsSeismic network · station log
Recording Stations11,803 Players69,659 Active3,689 Wipes · 3 h123 48 h

Station XX-15256 · no signal

[TEST] Dev Server

Offline 217.154.121.4:28015 checked 9d ago

moddedcarbon
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,256
top 69%
Last wipe
9d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15256 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k30 Sep5 Oct10 Oct15 Oct20 Oct25 Oct

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

Expected events

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 gap
1 daysbetween real wipes
on rhythm
50%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
0%else halves by day 1

The first 48 hours of its last wipes

Sat 17 OctSat 17 OctFri 16 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 17 Oct, 23:10 UTC9d ago M0.0steady 1 – running 1
Sat 17 Oct, 16:45 UTC10d ago M0.0rising 1 – 0.3 days 0
Fri 16 Oct, 21:07 UTC11d ago M0.0rising 1 – 0.8 days 0
Thu 15 Oct, 18:17 UTC12d ago M0.0rising 1 – 1.1 days 0
Fri 2 Oct, 20:54 UTC25d ago M0.0steady 1 halved by day 1 12.9 days 1
Thu 1 Oct, 20:09 UTC FW26d ago M0.0rising 1 – 1 days 0
Wed 30 Sep, 19:07 UTC27d ago M0.0rising 1 – 1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 164 on average
100/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average
131/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 112 on average
110/ 225
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
29/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 86 on average
96/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
34/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on [TEST] Dev Server?

No gather rate appears in the name of [TEST] Dev Server. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on [TEST] Dev Server right now?

A reading taken now finds [TEST] Dev Server offline; the most recent activity was 9 days 2 hours ago.

How does [TEST] Dev Server rank against other Rust servers?

On player hours for the past week, [TEST] Dev Server sits at #15,256, which puts it inside the top 69% of every ranked server.

Server facts

How reliably does [TEST] Dev Server stay online?

As recorded now, [TEST] Dev Server is not reachable, the last contact having been 9 days 2 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 30 September 2026.

Where in the world is [TEST] Dev Server hosted?

A region is not published by [TEST] Dev Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 217.154.121.4:28015 is the address it uses.

What build of Rust does [TEST] Dev Server use?

On Linux, [TEST] Dev Server runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on [TEST] Dev Server?

1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.

On what timetable does [TEST] Dev Server run its wipes?

No next wipe can be predicted for [TEST] Dev Server, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 9 days 23 hours is how long the current world has been running.

Server tags

What do the server tags on [TEST] Dev Server mean?

The game's server browser reads the tags [TEST] Dev Server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does [TEST] Dev Server appear?

You will find [TEST] Dev Server on the following Rust Server Trends lists: Modded Rust servers, tracked live. 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 2 weeks.

How to join

How do you connect to [TEST] Dev Server?

Enter client.connect 217.154.121.4:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build Game build: 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon Carbon is the plugin framework running 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.