Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 12hThu 5 Nov, 19:00 UTCFW
35d 12hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 15 Sep, 23:29 UTC43d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for #1 Rust Server Tool 420. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 172.59.97.116:28015.
How dependable is #1 Rust Server Tool 420, and is it online at the moment?
At this moment, #1 Rust Server Tool 420 is offline; the last time it was seen was 42 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 15 September 2026.
On what Rust version does #1 Rust Server Tool 420 sit?
The server #1 Rust Server Tool 420 is on Rust network protocol 2633 and build 163794 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does #1 Rust Server Tool 420 wipe its map?
#1 Rust Server Tool 420 wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 43 days 6 hours. Its tags record that it wipes monthly.
What happens on #1 Rust Server Tool 420 when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does #1 Rust Server Tool 420 place in the wider field of Rust servers?
Over the last seven days, #1 Rust Server Tool 420 has #15,502 for player hours, in the top – of all ranked servers.
How many players does #1 Rust Server Tool 420 usually have?
The last sighting of #1 Rust Server Tool 420 was 42 days 12 hours ago, and it is offline right now.
Tags and filters
What do #1 Rust Server Tool 420's tags stand for?
gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags #1 Rust Server Tool 420 publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does #1 Rust Server Tool 420 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include #1 Rust Server Tool 420: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
What settings and rules apply on #1 Rust Server Tool 420?
You will find no gather rate in the name of #1 Rust Server Tool 420. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map #1 Rust Server Tool 420 uses?
#1 Rust Server Tool 420 runs a procedural map, which the game generates.
How to join
How should you connect to #1 Rust Server Tool 420?
Enter client.connect 172.59.97.116:28015 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 asmp100,ptrak,$r?,v2633,^m,gmvanilla,cs163794,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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.
Not enough figures yet to write a report. Check back after a few days on the list.