Rust Server TrendsSeismic network · station log
Recording Stations11,525 Players85,836 Active3,992 Wipes · 3 h134 48 h

Station XX-15576 · no signal

HighwatchTest

Offline 64.52.206.216:28015 checked 14d ago

moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,576
top 71%
Last wipe
15d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15576 · 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 100 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 6 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
15k10k15k20k5 Nov7 Nov9 Nov10 Nov12 Nov14 Nov

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.

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

The first 48 hours of its last wipes

Fri 6 NovThu 5 Nov
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 6 Nov, 01:44 UTC15d ago M0.0rising 1 – running 0
Thu 5 Nov, 19:00 UTC FW15d ago – – – – – –
Thu 5 Nov, 12:54 UTC16d ago M0.0rising 1 – 0.5 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
123/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
299/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
188/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 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

Server rules

Which map is running on HighwatchTest?

HighwatchTest runs a procedural map of size 3,500 with seed 627073654, 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 HighwatchTest?

The name of HighwatchTest gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on HighwatchTest right now?

HighwatchTest is not responding at this moment and is offline, last seen 14 days 10 hours ago.

How does HighwatchTest rank against other Rust servers?

On player hours for the past week, HighwatchTest sits at #15,576, which puts it inside the top 71% of every ranked server.

Server details

How reliably does HighwatchTest stay online?

As recorded now, HighwatchTest is not reachable, the last contact having been 14 days 10 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 5 November 2026.

Where in the world is HighwatchTest hosted?

No region is published by HighwatchTest. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 64.52.206.216:28015 is the address it uses.

Which Rust version is HighwatchTest running?

On Windows, HighwatchTest runs Rust network protocol 2636 and build 170220. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on HighwatchTest?

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

On what timetable does HighwatchTest run its wipes?

The rhythm of HighwatchTest cannot yet be told: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 15 days 11 hours.

Lists and tags

What do the server tags on HighwatchTest mean?

These are the tags HighwatchTest publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs170220 (Build): The game build is 170220; 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; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 HighwatchTest appear?

These Rust Server Trends lists include HighwatchTest: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

How do you connect to HighwatchTest?

To join, enter client.connect 64.52.206.216: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 mp100,ptrak,$r?,v2636,gmrust,cs170220,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2636
Protocol To connect, your game must be on the same protocol, 2636.
cs170220
Build The game build is 170220.
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.

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.