Rust Server TrendsSeismic network · station log
Recording Stations11,614 Players32,078 Active2,758 Wipes · 3 h69 48 h

Station XX-16608 · no signal

Local Staging Test

Offline 213.193.252.202:28015 checked 27d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,608
top 70%
Last wipe
28d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16608 · 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 10 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 152 on average
44/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
62/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
18/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
4/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Local Staging Test?

The map on Local Staging Test is procedural, produced by the game.

Which settings and rules apply on Local Staging Test?

The name of Local Staging Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Local Staging Test?

No players are recorded on Local Staging Test at this moment; it is offline, and the last sighting was 27 days 19 hours ago.

How does Local Staging Test rank against other Rust servers?

On player hours for the past week, Local Staging Test sits at #16,608, which puts it inside the top 70% of every ranked server.

Server facts

How reliably does Local Staging Test stay online?

Local Staging Test is down at the moment; the last recorded contact was 27 days 19 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Local Staging Test hosted?

No region is published by Local Staging Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 213.193.252.202:28015.

What build of Rust does Local Staging Test use?

On Windows, Local Staging Test runs Rust network protocol 2634 and build 166427. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

How often does Local Staging Test wipe, and on which days?

On record so far are too few of Local Staging Test's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 28 days 8 hours is how long the current world has been running.

Tags

What do the server tags on Local Staging Test mean?

Tags published by Local Staging Test and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166427 (Build): The game build is 166427; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Local Staging Test appear?

You will find Local Staging Test on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto Local Staging Test?

You can connect by pressing F1 in Rust and typing client.connect 213.193.252.202:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166427,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166427
Build The game build is 166427.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.