Working its way up from the back of the class: #13,841 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
39/ 100
F
Slipped a little: down 3,128 places this week. Nothing a good wipe can't fix.
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.
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 61% 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 11h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
8d 11hThu 5 Nov, 19:00 UTCFW
36d 11hThu 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
Fri 25 Sep, 08:42 UTC32d 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 takes the server's word for its location and does not trace the hardware. Find it at 83.135.8.31:28015.
How reliable is #1 Rust Server Tool, and is it up?
You cannot join now: #1 Rust Server Tool is offline, last seen 32 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 24 September 2026, Rust Server Score saw it for the first time.
On what Rust version does #1 Rust Server Tool sit?
You will find #1 Rust Server Tool on Rust network protocol 2633 and build 165217, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does #1 Rust Server Tool wipe, and how often?
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. The world it runs now was created 32 days 22 hours. The tags show 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. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does #1 Rust Server Tool sit among Rust servers?
In the top 61% of all ranked servers, #1 Rust Server Tool sits at #13,841 for player hours over the last seven days.
How many players does #1 Rust Server Tool usually have?
It has been 32 days 20 hours since #1 Rust Server Tool was last seen, and it is offline right now.
Lists and filters
What do #1 Rust Server Tool's tags stand for?
gmvanilla (Game mode): You play vanilla survival here; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags #1 Rust Server Tool publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does #1 Rust Server Tool appear in the Rust Server Score lists and filters?
These Rust Server Score lists count #1 Rust Server Tool among them: 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
Which rules does #1 Rust Server Tool enforce, and what are its settings?
You will find no gather rate in the name of #1 Rust Server Tool. The group limit stays at the game's default of 8 players. It runs survival, 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. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map #1 Rust Server Tool uses?
#1 Rust Server Tool runs a procedural map, which the game generates.
Connecting
How should you connect to #1 Rust Server Tool?
Enter client.connect 83.135.8.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 asmp5,ptrak,$r?,v2633,^m,gmvanilla,cs165217,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.