Rust Server TrendsSeismic network · station log
Recording Stations11,695 Players53,611 Active3,212 Wipes · 3 h134 48 h

Station XX-16503 · no signal

TestServer

Offline 107.10.206.79:28015 checked 33d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,503
top 71%
Last wipe
34d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16503 · 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 10 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
15k10k15k20k24 Sep26 Sep27 Sep29 Sep30 Sep2 Oct

Top 71% 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, 1 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 25 Sep, 00:02 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 519 on average
361/ 400
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
336/ 350
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
38/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 276 on average
32/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
48/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 244 on average
175/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which settings and rules apply on TestServer?

The name of TestServer gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on TestServer right now?

A reading taken now finds TestServer offline; the most recent activity was 33 days 12 hours ago.

How does TestServer rank against other Rust servers?

Over the last seven days, TestServer recorded enough player hours to reach #16,503 worldwide, placing it in the top 71% of all ranked servers.

Server facts

How reliably does TestServer stay online?

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

Where in the world is TestServer hosted?

Nothing about a region comes from TestServer. 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 107.10.206.79:28015.

What build of Rust does TestServer use?

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

Wipe schedule

What does wipe day look like on TestServer?

The recent wipes averaged a busiest count of 1 players. 1 hours after the latest wipe, the crowd peaked.

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. 34 days 9 hours is how long the current world has been running.

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): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set. 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. 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.

How to join

How do you connect to TestServer?

You can connect by pressing F1 in Rust and typing client.connect 107.10.206.79: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build It runs game build 165217.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.