Rust Server TrendsSeismic network · station log
Recording Stations11,790 Players66,598 Active3,624 Wipes · 3 h126 48 h

Station XX-15126 · no signal

[TEST] The Test Server

Offline 116.89.111.196:28315 checked 12d ago

moddedoxide
Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,126
top 70%
Last wipe
24d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15126 · 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 1 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, measured since 17 Sep. 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
15k10k15k20k20 Sep26 Sep3 Oct9 Oct16 Oct22 Oct

Top 70% 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.

usual gap
17 daysbetween real wipes
wipe-day peak
0players, last three wipes
crowd held
0%else halves by day 1

The first 48 hours of its last wipes

Sun 4 OctThu 17 Sep
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
Sun 4 Oct, 14:17 UTC24d ago M0.0steady 0 – running 0
Thu 17 Sep, 15:15 UTC41d ago M0.0rising 1 halved by day 1 17 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
ShockRust | Blue | NoLimit no group limit · 157 on average
94/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
124/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
102/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 91 on average
82/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
28/ 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 [TEST] The Test Server?

Generated by the game, the map on [TEST] The Test Server is procedural, size 3,700 with seed 1845678248. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on [TEST] The Test Server?

No gather rate appears in the name of [TEST] The Test Server. 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. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on [TEST] The Test Server right now?

[TEST] The Test Server is not responding at this moment and is offline, last seen 12 days 22 hours ago.

How does [TEST] The Test Server rank against other Rust servers?

On player hours for the past week, [TEST] The Test Server sits at #15,126, which puts it inside the top 70% of every ranked server.

Server details

How reliably does [TEST] The Test Server stay online?

[TEST] The Test Server is down at the moment; the last recorded contact was 12 days 22 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 16 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does [TEST] The Test Server run from?

A region is not published by [TEST] The Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 116.89.111.196:28315 is the address it uses.

What build of Rust does [TEST] The Test Server use?

On Linux, [TEST] The Test Server runs Rust network protocol 2634 and build 166652. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on [TEST] The Test Server?

The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.

How often does [TEST] The Test Server wipe, and on which days?

Too few wipes of [TEST] The Test Server are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 24 days 6 hours.

Tags

What do the server tags on [TEST] The Test Server mean?

Tags published by [TEST] The Test Server and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): Slots: 1; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): It runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^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 [TEST] The Test Server appear?

The Rust Server Trends lists that take in [TEST] The Test Server are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto [TEST] The Test Server?

Enter client.connect 116.89.111.196:28315 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 mp1,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players Slots: 1.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166652
Build It runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.