Rust Server TrendsSeismic network · station log
Recording Stations11,669 Players34,137 Active2,836 Wipes · 3 h86 48 h

Station XX-14212 · no signal

test_server

Offline 46.63.106.19:28015 checked 27d ago

Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,212
top 60%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14212 · 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 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 60% 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 · 555 on average
136/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
118/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
13/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 286 on average
20/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
10/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average
18/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on test_server?

A procedural map runs on test_server, generated by the game.

Which settings and rules apply on test_server?

No gather rate appears in the name of test_server. At the game's default, groups can have up to 8 players. In survival 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. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on test_server right now?

test_server is not responding at this moment and is offline, last seen 27 days 15 hours ago.

How does test_server rank against other Rust servers?

On player hours for the past week, test_server sits at #14,212, which puts it inside the top 60% of every ranked server.

Server facts

How reliably does test_server stay online?

As recorded now, test_server is not reachable, the last contact having been 27 days 15 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does test_server run from?

A region is not published by test_server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 46.63.106.19:28015.

Which Rust version is test_server running?

Rust network protocol 2634 and build 166465 on Windows is what test_server runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

On what timetable does test_server run its wipes?

On record so far are too few of test_server'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. The present world dates from 27 days 17 hours.

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): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166465 (Build): It runs game build 166465; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. 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?

The Rust Server Trends lists that take in test_server 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.

Connecting

How do you connect to test_server?

Enter client.connect 46.63.106.19: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 mp10,ptrak,$r?,v2634,gmrust,cs166465,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166465
Build It runs game build 166465.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

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.