Rust Server TrendsSeismic network · station log
Recording Stations11,672 Players47,205 Active2,988 Wipes · 3 h97 48 h

Station XX-13909 · no signal

TestServer

Offline 119.228.206.30:28015 checked 26d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#13,909
top 61%
Last wipe
28d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13909 · 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 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. 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
15k10k15k20k2 Oct4 Oct5 Oct7 Oct8 Oct10 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

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 · 486 on average
46/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 321 on average
78/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 283 on average
256/ 300
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 279 on average
11/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
313/ 375
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 256 on average
267/ 300
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on TestServer?

The map on TestServer is procedural, produced by the game.

Which settings and rules apply on TestServer?

No gather rate appears in the name of TestServer. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on TestServer right now?

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

How does TestServer rank against other Rust servers?

On player hours for the past week, TestServer sits at #13,909, which puts it inside the top 61% of every ranked server.

Operator and location

How reliably does TestServer stay online?

No contact with TestServer right now, and the last recorded contact was 26 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 2 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does TestServer run from?

No region is published by TestServer. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 119.228.206.30:28015.

What build of Rust does TestServer use?

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

Wipe day

On what timetable does TestServer run its wipes?

Too few wipes of TestServer are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 28 days 4 hours.

Server tags

What do the server tags on TestServer mean?

These are the tags TestServer publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): Slots: 1; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. 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?

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

How do you connect to TestServer?

To join, enter client.connect 119.228.206.30: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 mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players Slots: 1.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166494
Build Game build: 166494.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.