RUST METRICSFlight deck · live data
Data live Servers11,694 Players45,403 Populated3,140 Fresh wipes 3 h97 Scan5 min
‹ All servers66.51.99.4:40123
Online Full Queue Fresh wipe Wipe due No query

HighMiles Test server

Online 66.51.99.4:40123 checked 11m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 23:00 UTC
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 14 SERVER FPS

Server fps

48 h low 7 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 79,536 ×1000

Entities

48 h range 72,206–125,964 · memory 3,063 MB
1239 ET SINCE RESTART 03:14

Uptime

3 h 14 min since its last restart, at the last reading
7-day average0peak 2
Rank#9,946top 45%
Last wipe5h agono schedule published
Next wipe–no rhythm it keeps
Memory3,063MB48 h peak 2 players
REC 1

Players

AveragePeakWipe
00.511.5201:0010:0019:0004:0013:0023:00Wiped Wed 28 Oct, 19:49 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
0510152001:0010:0019:0004:0013:0023:00Wiped Wed 28 Oct, 19:49 UTCWIPE

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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct18 Oct23 Oct28 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 23 OctThu 22 OctSun 18 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 19:49 UTC5h ago – – running 0
Fri 23 Oct, 23:57 UTC5d ago 1 – – 0
Thu 22 Oct, 20:46 UTC6d ago 1 – 1.1 days 0
Sun 18 Oct, 01:06 UTC10d ago 1 halved by day 1 4.8 days 0
Sat 17 Oct, 04:16 UTC11d ago 1 – 0.9 days 0
Fri 16 Oct, 17:32 UTC12d ago 2 – 0.4 days 0
Thu 15 Oct, 04:04 UTC13d ago 2 – 1.6 days 0
Wed 14 Oct, 19:53 UTC14d ago 2 – 0.3 days 0
Tue 13 Oct, 20:56 UTC15d ago 1 – 1 days 0
Sat 10 Oct, 21:52 UTC18d ago 1 held half 3 days 0

Peak: the most players in the first 48 hours. 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on HighMiles Test server when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 1 it fell below half when it didn't.

When does HighMiles Test server wipe?

There is no next wipe to predict: HighMiles Test server wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 5 hours ago the current world was made.

Tag meanings

How should you read the tags on HighMiles Test server?

These are the tags HighMiles Test server publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does HighMiles Test server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry HighMiles Test server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.

Population

What position does HighMiles Test server hold among Rust servers?

Player hours over seven days put HighMiles Test server at #9,946, in the top 45% of all ranked servers.

What is the population on HighMiles Test server?

Current headcount on HighMiles Test server: 0 players, 10 slots available. Seven-day check: 0 players on average. Peak reading: 2. Average at the busiest hour was 1 players, at 20:00 UTC over the last 48 hours.

Server

Where does HighMiles Test server sit?

Reading: location. HighMiles Test server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 66.51.99.4:40123.

What Rust version is HighMiles Test server on?

Rust network protocol 2635 and build 168909 on Linux is the build HighMiles Test server runs. Matching protocol is required to join. Let Steam update your game.

How does HighMiles Test server perform?

Over the last 48 hours the average was 14 server fps; the floor was 7. Peak entity count: 125,964. Buildings, deployables and all else included. Reading: 12,232 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is HighMiles Test server, and is it online now?

Check: connection. HighMiles Test server is online at this moment. Check: restart. The uptime it reports puts the last restart about 3 hours ago. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. The first sighting on Rust Metrics was 3 October 2026.

Rules and settings

How is HighMiles Test server configured, and what rules are in force?

No gather rate appears in the name: HighMiles Test server. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is HighMiles Test server on?

From seed 1337, the game generates the procedural map on HighMiles Test server. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Custom Map.

Connection

What do you do to join HighMiles Test server?

Check: join. Open Rust, press F1, then enter client.connect 66.51.99.4:40123. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://highs-pve-server.paynow.store/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.