Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-13426 · no signal

My Local Test

Offline 89.255.97.240:28015 checked 37d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,426
top 62%
Last wipe
44d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-13426 · 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
15k10k15k20k2 Oct6 Oct10 Oct14 Oct18 Oct22 Oct

Top 62% 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.7 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctMon 5 OctSun 4 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, 2 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –
Wed 7 Oct, 21:02 UTC44d ago M0.0rising 1 – – 0
Mon 5 Oct, 22:46 UTC46d ago M0.0rising 1 – 1.9 days 0
Sun 4 Oct, 12:35 UTC48d ago M0.0rising 1 – 1.4 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
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
123/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
299/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
115/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
14/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on My Local Test?

My Local Test uses a procedural map, which the game generates.

Which settings and rules apply on My Local Test?

No gather rate appears in the name of My Local Test. 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. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on My Local Test right now?

My Local Test is not responding at this moment and is offline, last seen 37 days 11 hours ago.

How does My Local Test rank against other Rust servers?

On player hours for the past week, My Local Test sits at #13,426, which puts it inside the top 62% of every ranked server.

Server details

How reliably does My Local Test stay online?

My Local Test is down at the moment; the last recorded contact was 37 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 2 October 2026 is when Rust Server Trends first recorded it.

Which region does My Local Test run from?

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

Which Rust version is My Local Test running?

Rust network protocol 2634 and build 166652 on Windows is what My Local Test runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on My Local Test?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 2 hours after the wipe.

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

No next wipe can be predicted for My Local Test, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. 44 days 15 hours is how long the current world has been running.

Server tags

What do the server tags on My Local Test mean?

These are the tags My Local Test publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; 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; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs 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 Local Test appear?

These Rust Server Trends lists include My Local Test: 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.

Join the server

How do you connect to My Local Test?

To join, enter client.connect 89.255.97.240: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,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
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.
cs166652
Build Game build: 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs 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.