Working its way up from the back of the class: #12,988 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
32/ 100
F
Lost ground: down 4,576 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeak
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 59% of all ranked servers. Ranked on player hours over the last seven days.
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 8d 15h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
8d 15hThu 5 Nov, 19:00 UTCFW
36d 15hThu 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, 46 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 18:51 UTC25d ago
1
–
running
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
#1 Rust Server Tool leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 45.6.40.4:28015.
How reliable is #1 Rust Server Tool, and is it up?
You cannot join now: #1 Rust Server Tool is offline, last seen 9 days 5 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 18 September 2026.
On what Rust version does #1 Rust Server Tool sit?
Rust network protocol 2634 and build 167781 on Windows is what #1 Rust Server Tool runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does #1 Rust Server Tool reset?
The force wipe each month is the only wipe #1 Rust Server Tool takes. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 25 days 8 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What happens on #1 Rust Server Tool when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 46 hours into the latest wipe.
Player count
Where does #1 Rust Server Tool sit among Rust servers?
Over the last seven days, #1 Rust Server Tool has #12,988 for player hours, in the top 59% of all ranked servers.
What does the population on #1 Rust Server Tool look like?
The last sighting of #1 Rust Server Tool was 9 days 5 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on #1 Rust Server Tool?
You'll see #1 Rust Server Tool tagged with gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. 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 #1 Rust Server Tool?
Rust Server Score lists that include #1 Rust Server Tool: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
How is #1 Rust Server Tool set up, and what rules does it keep?
The name of #1 Rust Server Tool gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: 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. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
#1 Rust Server Tool runs which map?
The game generates a procedural map for #1 Rust Server Tool.
How to join
How should you connect to #1 Rust Server Tool?
To connect, start Rust, press F1, and type client.connect 45.6.40.4:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^m,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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. Even marks across the subjects, from F to F.