Rust Server TrendsSeismic network · station log
Recording Stations11,524 Players85,475 Active3,973 Wipes · 3 h131 48 h

Station XX-15479 · no signal

Testserver

Offline 46.0.24.240:38015 checked 9d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,479
top 70%
Last wipe
9d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15479 · 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, measured since 12 Nov. 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
15k10k15k20k11 Nov13 Nov14 Nov16 Nov17 Nov19 Nov

Top 70% 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.

usual gap
0.3 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Thu 12 NovWed 11 Nov
01234+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
Thu 12 Nov, 06:53 UTC9d ago M0.0steady 0 – running 0
Wed 11 Nov, 23:33 UTC9d ago M0.0steady 0 – 0.3 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
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
122/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
298/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
189/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
65/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
115/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
14/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Testserver?

Testserver runs a procedural map of size 1,000 with seed 666, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on Testserver?

The name of Testserver gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on Testserver?

A reading taken now finds Testserver offline; the most recent activity was 9 days 5 hours ago.

How does Testserver rank against other Rust servers?

On player hours for the past week, Testserver sits at #15,479, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does Testserver stay online?

As recorded now, Testserver is not reachable, the last contact having been 9 days 5 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 11 November 2026 it was recorded for the first time by Rust Server Trends.

Which region does Testserver run from?

A region is not published by Testserver. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 46.0.24.240:38015.

What build of Rust does Testserver use?

Rust network protocol 2636 and build 170545 on Linux is what Testserver runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on Testserver?

The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does Testserver run its wipes?

On record so far are too few of Testserver's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 3 December at 19:00 UTC. The present world dates from 9 days 6 hours.

Server tags

What do the server tags on Testserver mean?

These are the tags Testserver publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170545 (Build): The game build is 170545; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Join the server

How do you connect to Testserver?

To join, enter client.connect 46.0.24.240:38015 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 mp10,ptrak,$r?,v2636,gmvanilla,cs170545,ts8,^o^z

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs170545
Build The game build is 170545.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.