Rust Server TrendsSeismic network · station log
Recording Stations11,626 Players31,131 Active2,740 Wipes · 3 h70 48 h

Station XX-15464 · no signal

TestServer

Offline 149.202.227.169:28015 checked 43d ago

Connect
Players now
0/ 3
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,464
no region published
Last wipe
55d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15464 · 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 3 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 Sep21 Sep22 Sep
Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 542 on average
145/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
131/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
15/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 283 on average
19/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
16/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 249 on average
46/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on TestServer?

TestServer uses a procedural map, which the game generates.

Which settings and rules apply on TestServer?

You will find no gather rate in the name of TestServer. The group limit is 8 players, the game's default. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on TestServer right now?

TestServer is not responding at this moment and is offline, last seen 43 days 8 hours ago.

How does TestServer rank against other Rust servers?

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

Server facts

How reliably does TestServer stay online?

TestServer is down at the moment; the last recorded contact was 43 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does TestServer run from?

Nothing about a region comes from TestServer. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 149.202.227.169:28015.

What build of Rust does TestServer use?

TestServer is running Rust network protocol 2633 and build 163794 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

On what timetable does TestServer run its wipes?

On record so far are too few of TestServer's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 55 days 11 hours is how long the current world has been running.

Tags

What do the server tags on TestServer mean?

The game's server browser reads the tags TestServer publishes: gmvanilla (Game mode): Survival in vanilla mode; mp3 (Max players): 3 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163794 (Build): It runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. Current players, queue length and world creation time sit in the tags as well, and appear 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: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

What steps get you onto TestServer?

You can connect by pressing F1 in Rust and typing client.connect 149.202.227.169: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 mp3,ptrak,$r?,v2633,gmvanilla,cs163794,ts8

Game

gmvanilla
Game mode Survival in vanilla mode.
mp3
Max players 3 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs163794
Build It runs game build 163794.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.