Rust Server TrendsSeismic network · station log
Recording Stations11,824 Players75,694 Active3,728 Wipes · 3 h230 48 h

Station XX-15366 · no signal

:thinking:

Offline 203.94.34.210:28020 checked 16d ago

moddedoxide
Connect
Players now
0/ 200
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,366
top 71%
Last wipe
16d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15366 · 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 200 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
15k10k15k20k6 Oct9 Oct12 Oct14 Oct17 Oct20 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 13 Oct, 12:22 UTC16d ago M0.0steady 0 – – running 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
1403/ 2000
R2 - Aim training / Matchmaking / Facechecks - RU Main EU · groups of 12+ · 219 on average
503/ 550
RustGames.gg | Lucky Pillars - EU 1 EU · groups of 100+ · 83 on average
159/ 400
DOGFIGHT 2 | BATTLEFIELD/HELI/MINI/FFA/MM/AIMTRAINING/PVP groups of 30+ · weekly · 69 on average
171/ 250
R2 - Aim training / Matchmaking / Facechecks - EU Main EU · groups of 12+ · 37 on average
126/ 400
[EU] BekerMelk's Bow Aim Training Server | AimTrain | ukNLD EU · no group limit · 30 on average
102/ 125
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on :thinking:?

You will find no gather rate in the name of :thinking:. 90 players is the most a group can hold. In minigames & battle royale mode, battle royale, arenas, parkour and Bedwars. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on :thinking: right now?

:thinking: is not responding at this moment and is offline, last seen 16 days 1 hours ago.

How does :thinking: rank against other Rust servers?

On player hours for the past week, :thinking: sits at #15,366, which puts it inside the top 71% of every ranked server.

Server facts

How reliably does :thinking: stay online?

No contact with :thinking: right now, and the last recorded contact was 16 days 1 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is :thinking: hosted?

A region is not published by :thinking:. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 203.94.34.210:28020.

What build of Rust does :thinking: use?

On Windows, :thinking: runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on :thinking:?

On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.

How often does :thinking: wipe, and on which days?

The rhythm of :thinking: cannot yet be told: too few of its wipes are on record. 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 16 days 1 hours.

Server tags

What do the server tags on :thinking: mean?

These are the tags :thinking: publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp200 (Max players): 200 slots are available; ts90 (Group limit): Teams are capped at 90 players; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): Game build: 167781; 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; ^e (Minigames): Minigames are the focus, such as arenas, Bedwars and parkour; ^d (Combat training): Practise aim and PvP with loot provided; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 :thinking: appear?

You will find :thinking: on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust aim training servers, live. You will find it under these filters on the server list: Type: Modded; Server tag: Minigames ^e, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto :thinking:?

To join, enter client.connect 203.94.34.210:28020 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 mp200,ptrak,$r?,v2634,^e,^d,gmrust,cs167781,ts90,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp200
Max players 200 slots are available.
ts90
Group limit Teams are capped at 90 players.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167781
Build Game build: 167781.
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.

Gameplay

^e
Minigames Minigames are the focus, such as arenas, Bedwars and parkour.
^d
Combat training Practise aim and PvP with loot provided.

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.