Rust Server TrendsSeismic network · station log
Recording Stations11,830 Players85,544 Active3,690 Wipes · 3 h401 48 h

Station XX-12870 · recording

Test

Online 66.51.99.64:28035 checked 12m ago

monthly wipes moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#12,870
top 58%
Last wipe
28d ago
monthly schedule
Next wipe
6d 21h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-12870 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Thu 05:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75122:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

0510152022:0007:0016:0002:0011:0020:00

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 17 Sep. 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 Sep28 Sep5 Oct13 Oct21 Oct29 Oct

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

Expected events

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. The force wipe · high confidence

usual gap
0.6 daysbetween real wipes
wipe-day peak
1players, last three wipes

Coming wipes

  1. 6d 21hThu 5 Nov, 19:00 UTCFW
  2. 34d 21hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 1 OctThu 1 Oct
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
Thu 1 Oct, 17:57 UTC FW28d ago M0.0rising 1 – running 0
Thu 1 Oct, 04:17 UTC28d ago M0.0rising 1 – 0.6 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
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
33/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 92 on average
99/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
10/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 EU · groups of 16+ · monthly · 77 on average
81/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 EU · groups of 16+ · monthly · 73 on average
168/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 EU · groups of 16+ · monthly · 70 on average
257/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Test?

Test runs a procedural map of size 5,000 with seed 1337, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. The name of its map is Custom Map.

Which settings and rules apply on Test?

You will find no gather rate in the name of Test. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on Test right now?

At this moment, Test records 0 players across 50 slots. Across seven days this server recorded an average of 0 players and a peak of 1. Averaged over the last 48 hours, the busiest hour was 05:00 UTC at 1 players.

How does Test rank against other Rust servers?

The last seven days of player hours place Test at #12,870, in the top 58% of all ranked servers.

Operator and location

How reliably does Test stay online?

As recorded now, Test is running. Its reported uptime points to a restart about 6 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does Test perform under load?

Across the last 48 hours it averaged 6 server fps, with a floor of 5. At its highest, it carried 125,890 entities: buildings, deployables and the world's other contents. Memory use peaked at 6,871 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does Test run from?

No region is published by Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 66.51.99.64:28035.

What build of Rust does Test use?

Rust network protocol 2635 and build 168909 on Linux is what Test runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Test?

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

How often does Test wipe, and on which days?

The force wipe is the only wipe Test takes, once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 28 days 3 hours. Its tags state a monthly wipe schedule.

Lists and tags

What do the server tags on Test mean?

These are the tags Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. 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 Test appear?

You will find Test on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Connecting

How do you connect to Test?

Enter client.connect 66.51.99.64:28035 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 mp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players Slots: 50.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Wipe schedule

^m
Monthly Wipes happen monthly, at the same time as Facepunch's force wipe.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.