Rust Server TrendsSeismic network · station log
Recording Stations11,793 Players79,700 Active3,567 Wipes · 3 h247 48 h

Station XX-15341 · no signal

TestServer

Offline 160.251.212.33:28015 checked 7d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,341
top 69%
Last wipe
34d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15341 · 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 50 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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 25 Sep, 04:23 UTC34d ago M0.0rising 1 – 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 · 150 on average
39/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
132/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average
86/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
32/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 92 on average
86/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
309/ 350
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on TestServer?

Generated by the game, the map on TestServer is procedural, size 3,000 with seed 15111. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on TestServer?

You will find no gather rate in the name of TestServer. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on TestServer right now?

TestServer is not responding at this moment and is offline, last seen 7 days 16 hours ago. The seven-day average for this server is 0 players.

How does TestServer rank against other Rust servers?

On player hours for the past week, TestServer sits at #15,341, which puts it inside the top 69% of every ranked server.

Server details

How reliably does TestServer stay online?

TestServer is down at the moment; the last recorded contact was 7 days 16 hours ago. 7 of 168 hours in the last 7 full days were up time, 4% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

Where in the world is TestServer hosted?

A region is not published by TestServer. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 160.251.212.33:28015 is the address it uses.

Which Rust version is TestServer running?

TestServer is running Rust network protocol 2633 and build 162929 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on TestServer?

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

How often does TestServer wipe, and on which days?

On record so far are too few of TestServer's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 34 days 16 hours.

Server tags

What do the server tags on TestServer mean?

Tags published by TestServer and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs162929 (Build): Game build: 162929; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $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 TestServer appear?

The Rust Server Trends lists that take in TestServer are: 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

How do you connect to TestServer?

You can connect by pressing F1 in Rust and typing client.connect 160.251.212.33:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players The server has 50 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs162929
Build Game build: 162929.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.