Rust Server TrendsSeismic network · station log
Recording Stations11,881 Players89,789 Active4,026 Wipes · 3 h157 48 h

Station XX-15346 · no signal

TEST Server

Offline 106.153.36.63:28015 checked 14d ago

Connect
Players now
0/ 5
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,346
top 71%
Last wipe
14d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15346 · 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 5 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
15k10k15k20k20 Sep24 Sep7 Oct11 Oct16 Oct20 Oct

Top 71% 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
4 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
1players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 13 OctWed 7 OctWed 7 Oct
00.250.50.751+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
Tue 13 Oct, 15:09 UTC14d ago M0.0steady 0 – – running 0
Wed 7 Oct, 10:46 UTC20d ago M0.0rising 1 – 6.2 days 0
Wed 7 Oct, 02:16 UTC20d ago M0.0rising 1 – 0.4 days 0
Mon 5 Oct, 04:47 UTC22d ago M0.0steady 1 – 1.9 days 1
Sun 13 Sep, 11:11 UTC44d ago M0.0rising 1 held half 21.7 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 504 on average
789/ 825
Rustoria.co - EU Main EU · groups of 16+ · weekly · 345 on average
47/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 340 on average
122/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 314 on average
404/ 500
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 280 on average
260/ 300
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 259 on average
186/ 300
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on TEST Server?

No gather rate appears in the name of TEST Server. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched off.

Live population

How many players are recorded on TEST Server right now?

A reading taken now finds TEST Server offline; the most recent activity was 14 days 4 hours ago.

How does TEST Server rank against other Rust servers?

Over the last seven days, TEST Server recorded enough player hours to reach #15,346 worldwide, placing it in the top 71% of all ranked servers.

Operator and location

How reliably does TEST Server stay online?

No contact with TEST Server right now, and the last recorded contact was 14 days 4 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Which region does TEST Server run from?

Nothing about a region comes from TEST Server. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 106.153.36.63:28015.

What build of Rust does TEST Server use?

TEST Server is running Rust network protocol 2634 and build 167781 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on TEST Server?

The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does TEST Server wipe, and on which days?

There is no next wipe to predict at TEST Server, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 14 days 4 hours is how long the current world has been running.

Lists and tags

What do the server tags on TEST Server mean?

The game's server browser reads the tags TEST Server publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): Slots: 5; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. 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: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto TEST Server?

Enter client.connect 106.153.36.63: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 mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp5
Max players Slots: 5.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs167781
Build It runs game build 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.