Rust Server TrendsSeismic network · station log
Recording Stations11,748 Players75,412 Active3,731 Wipes · 3 h135 48 h

Station XX-13806 · no signal

Local Staging Test

Offline 175.38.78.203:28015 checked 26d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,806
top 60%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13806 · 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
1of 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 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 60% 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 543 on average
679/ 725
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
429/ 475
Rustoria.co - EU Main EU · groups of 16+ · weekly · 308 on average
40/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 308 on average
52/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 268 on average
228/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 266 on average
134/ 175
Readings, in words

Quick answers

from the figures on this page

Map and rules

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. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Population

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 26 days 3 hours ago.

How does Local Staging Test rank against other Rust servers?

The last seven days of player hours place Local Staging Test at #13,806, in the top 60% of all ranked servers.

Server facts

How reliably does Local Staging Test stay online?

As recorded now, Local Staging Test is not reachable, the last contact having been 26 days 3 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Local Staging Test hosted?

Nothing about a region comes from Local Staging Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 175.38.78.203:28015 is the address it uses.

What build of Rust does Local Staging Test use?

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

Wipe schedule

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

Too few wipes of Local Staging Test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 2 hours.

Lists and tags

What do the server tags on Local Staging Test mean?

The game's server browser reads the tags Local Staging Test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; 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; cs166465 (Build): Game build: 166465; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. 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?

These Rust Server Trends lists include Local Staging Test: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

How do you connect to Local Staging Test?

To join, enter client.connect 175.38.78.203:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166465,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players Slots: 10.
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.
cs166465
Build Game build: 166465.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.