Fig. 1Players on HighMiles Test serverRG-S9954-01 · Sheet 1 of 10
Fig. 2
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S9954-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 45% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S9954-03 · Sheet 3 of 10
Schedule
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
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
ScheduleExpected wipesRG-S9954-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 19:49 UTC5h ago
–
–
running
0
Fri 23 Oct, 23:57 UTC5d ago
1
halved by day 1
4.8 days
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
Sat 10 Oct, 13:05 UTC18d ago
1
–
0.4 days
1
Tue 6 Oct, 00:20 UTC23d ago
1
held half
4.5 days
1
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.
Table 1Wipe logRG-S9954-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
How reliable is HighMiles Test server, and is it online now?
HighMiles Test server is up at this moment. The uptime it reports puts the last restart at about 3 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. The first sighting of it by Rust Graphs was on 3 October 2026.
2.
What does the recorded performance of HighMiles Test server show?
14 server fps on average over the last 48 hours, and never under 7. Counted at its highest: 125,964 entities, buildings, deployables and the rest of the world included. Memory use peaked at 12,232 MB. A climbing entity count and low fps are the source of what players feel as lag.
3.
In which location is HighMiles Test server hosted?
There is no region published by HighMiles Test server. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 66.51.99.4:40123 is its address.
4.
What Rust version is recorded for HighMiles Test server?
Rust network protocol 2635 and build 168909 on Linux: that is what HighMiles Test server runs. To join, your game must be on the same protocol; Steam handles the update.
Counts
5.
What player count is recorded on HighMiles Test server?
At the last refresh, HighMiles Test server recorded 0 players across 10 slots. Averaged across seven days, the player count is 0, with a peak of 2. Over the last 48 hours the busiest hour was 20:00 UTC, at an average of 1 players.
6.
Against other Rust servers, where is HighMiles Test server placed?
Over the last seven days, HighMiles Test server records #9,954 for player hours: the top 45% of all ranked servers.
Schedules
7.
What happens on HighMiles Test server on the day of a wipe?
An average of 1 players was recorded at the busiest point of its recent wipes. 1 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 1.
8.
What wipe schedule has been recorded for HighMiles Test server?
There is no next wipe to predict at HighMiles Test server, which wipes at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The current world has been in use since 5 hours ago.
Map and rules
9.
What settings and rules apply on HighMiles Test server?
Gather rate for HighMiles Test server: not stated in the name. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.
10.
What is the map for HighMiles Test server?
HighMiles Test server runs a procedural map of size 3,500 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.
Lists and filters
11.
Where does HighMiles Test server appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry HighMiles Test server are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
12.
Which meaning is attached to each tag on HighMiles Test server?
Tags published by HighMiles Test server, and read by the game's server browser: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
13.
How is HighMiles Test server joined?
Connect with client.connect 66.51.99.4:40123: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://highs-pve-server.paynow.store/ is its website.
NotesAnswered from the figuresRG-S9954-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp10
Max playersThe slot count is 10.
ts8
Group limitTeams are capped at 8, the default setting.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingStandard network layer: RakNet.
$r?
Region codeThe region code field is empty.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is 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.
