Working its way up from the back of the class: #15,423 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 250 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Rust Hunter | LOCAL TEST leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 176.124.17.231:28115 is the address to use.
How reliable is Rust Hunter | LOCAL TEST, and is it up?
You cannot join now: Rust Hunter | LOCAL TEST is offline, last seen 7 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 20 October 2026.
Which Rust version is Rust Hunter | LOCAL TEST running?
You will find Rust Hunter | LOCAL TEST on Rust network protocol 2634 and build 167781, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Rust Hunter | LOCAL TEST wipe, and how often?
There are too few wipes on record for Rust Hunter | LOCAL TEST to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 8 days 21 hours.
Population
Where does Rust Hunter | LOCAL TEST sit among Rust servers?
In the top 69% of all ranked servers, Rust Hunter | LOCAL TEST sits at #15,423 for player hours over the last seven days.
Is Rust Hunter | LOCAL TEST a busy server?
The last sighting of Rust Hunter | LOCAL TEST was 7 days 21 hours ago, and it is offline right now.
Tags
What do Rust Hunter | LOCAL TEST's tags stand for?
The game's browser takes its cue from the tags Rust Hunter | LOCAL TEST has set: gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): The server holds 5 slots; ts5 (Group limit): No team may go above 5; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Rust Hunter | LOCAL TEST?
These Rust Server Score lists count Rust Hunter | LOCAL TEST among them: Modded Rust servers, graded. It shows under the following 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.
Server rules
Which rules does Rust Hunter | LOCAL TEST enforce, and what are its settings?
Nothing in the name of Rust Hunter | LOCAL TEST states a gather rate. A group here can reach 5 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Rust Hunter | LOCAL TEST runs which map?
The game generates a procedural map for Rust Hunter | LOCAL TEST.
Getting in
What is the way to join Rust Hunter | LOCAL TEST?
Enter client.connect 176.124.17.231:28115 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,gmrust,cs167781,ts5,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp5
Max playersThe server holds 5 slots.
ts5
Group limitNo team may go above 5.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).