Working its way up from the back of the class: #13,650 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
46/ 100
D
Slipped a little: down 1,085 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 62% 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h.
The 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
No region is published for #1 Rust Server Tool. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 190.231.246.31:28015 is the address to use.
Is #1 Rust Server Tool up, and how steady is its uptime?
The server is down: #1 Rust Server Tool is offline now, with the last sighting 20 days 12 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 8 October 2026.
Which Rust version is #1 Rust Server Tool running?
The server #1 Rust Server Tool is on Rust network protocol 2634 and build 167231 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does #1 Rust Server Tool reset?
The estimate for #1 Rust Server Tool's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 20 days 14 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player numbers
Where does #1 Rust Server Tool place in the wider field of Rust servers?
In the top 62% of all ranked servers, #1 Rust Server Tool sits at #13,650 for player hours over the last seven days.
How many players does #1 Rust Server Tool usually have?
The last sighting of #1 Rust Server Tool was 20 days 12 hours ago, and it is offline right now.
Tags and filters
What do #1 Rust Server Tool's tags stand for?
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): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. 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 appear in the Rust Server Score lists and filters?
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 Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
What settings and rules apply on #1 Rust Server Tool?
You will find no gather rate in the name of #1 Rust Server Tool. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: 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. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on #1 Rust Server Tool?
A procedural map, generated by the game, is what #1 Rust Server Tool runs.
How to join
What is the way to join #1 Rust Server Tool?
Enter client.connect 190.231.246.31: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?,v2634,^z,^y,^m,gmvanilla,cs167231,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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 D.