Rust Server TrendsSeismic network · station log
Recording Stations11,873 Players96,161 Active3,898 Wipes · 3 h387 48 h

Station XX-13364 · no signal

Test Server

Offline 106.178.130.181:28015 checked 17d ago

moddedoxide
Connect
Players now
1/ 32
3% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,364
top 61%
Last wipe
17d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-13364 · 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 32 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
15k10k15k20k21 Sep24 Sep27 Sep13 Oct16 Oct19 Oct

Top 61% 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
1players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 12 Oct, 11:11 UTC17d ago M0.0steady 1 – running 1

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 · 150 on average
166/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
185/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
81/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 87 on average
258/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average
349/ 350
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Test Server?

Test Server uses a procedural map, which the game generates.

Which settings and rules apply on Test Server?

You will find no gather rate in the name of Test Server. 32 players is the most a group can hold. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on Test Server?

A reading taken now finds Test Server offline; the most recent activity was 17 days 2 hours ago.

How does Test Server rank against other Rust servers?

The last seven days of player hours place Test Server at #13,364, in the top 61% of all ranked servers.

Server details

How reliably does Test Server stay online?

As recorded now, Test Server is not reachable, the last contact having been 17 days 2 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 21 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Test Server hosted?

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

What build of Rust does Test Server use?

On Windows, Test Server runs Rust network protocol 2634 and build 167584. 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 Server?

1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.

On what timetable does Test Server run its wipes?

Too few wipes of 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 17 days 5 hours.

Server tags

What do the server tags on Test Server mean?

The game's server browser reads the tags Test Server publishes: gmrust (Game mode): Survival in standard Rust; mp32 (Max players): 32 slots are available; ts32 (Group limit): Teams are capped at 32 players; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167584 (Build): Game build: 167584; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^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 Server appear?

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

How do you connect to Test Server?

To join, enter client.connect 106.178.130.181: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 mp32,ptrak,$r?,v2634,gmrust,cs167584,ts32,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp32
Max players 32 slots are available.
ts32
Group limit Teams are capped at 32 players.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167584
Build Game build: 167584.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.