Rust Server TrendsSeismic network · station log
Recording Stations11,716 Players55,754 Active3,252 Wipes · 3 h168 48 h

Station XX-15825 · no signal

My Server Name+server.port

Offline 31.134.43.62:28015 checked 19d ago

moddedoxide
Connect
Players now
0/ 500
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,825
top 72%
Last wipe
19d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15825 · 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 500 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
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

Top 72% 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

01234+0h+9h+19h+28h+38h+47h

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
Sat 10 Oct, 08:25 UTC19d 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
ShockRust | Blue | NoLimit no group limit · 149 on average
143/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
122/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
184/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
78/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
7/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
18/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on My Server Name+server.port?

The map on My Server Name+server.port is procedural, produced by the game.

Which settings and rules apply on My Server Name+server.port?

The name of My Server Name+server.port gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on My Server Name+server.port?

My Server Name+server.port is not responding at this moment and is offline, last seen 19 days ago.

How does My Server Name+server.port rank against other Rust servers?

Over the last seven days, My Server Name+server.port recorded enough player hours to reach #15,825 worldwide, placing it in the top 72% of all ranked servers.

Server details

How reliably does My Server Name+server.port stay online?

As recorded now, My Server Name+server.port is not reachable, the last contact having been 19 days ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 10 October 2026.

Which region does My Server Name+server.port run from?

A region is not published by My Server Name+server.port. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 31.134.43.62:28015 is the address it uses.

What build of Rust does My Server Name+server.port use?

My Server Name+server.port is running Rust network protocol 2634 and build 167398 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on My Server Name+server.port?

The recent wipes averaged a busiest count of 0 players. The peak on the most recent wipe came 0 hours after the wipe.

On what timetable does My Server Name+server.port run its wipes?

The rhythm of My Server Name+server.port cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 19 days 1 hours is how long the current world has been running.

Server tags

What do the server tags on My Server Name+server.port mean?

Tags published by My Server Name+server.port and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp500 (Max players): The server has 500 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it 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 My Server Name+server.port appear?

These Rust Server Trends lists include My Server Name+server.port: 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 My Server Name+server.port?

Enter client.connect 31.134.43.62: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 mp500,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp500
Max players The server has 500 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167398
Build Game build: 167398.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.