Working its way up from the back of the class: #14,305 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,029 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.
No daily history yet.
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
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 2h.
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 takes the server's word for its location and does not trace the hardware. 179.108.37.14:28015 is the address to use.
Is #1 Rust Server Tool up, and how steady is its uptime?
At this moment, #1 Rust Server Tool is offline; the last time it was seen was 33 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 26 September 2026.
On what Rust version does #1 Rust Server Tool sit?
Rust network protocol 2633 and build 165217 on Windows is what #1 Rust Server Tool runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does #1 Rust Server Tool reset?
The estimate for #1 Rust Server Tool's next wipe comes from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 33 days 19 hours. Its tags record that it wipes monthly.
Player count
What position does #1 Rust Server Tool hold in the rankings?
Over the last seven days, #1 Rust Server Tool has #14,305 for player hours, in the top 61% of all ranked servers.
How many players does #1 Rust Server Tool usually have?
The last sighting of #1 Rust Server Tool was 33 days 1 hours ago, and it is offline right now.
Tags
How should you read the tags on #1 Rust Server Tool?
The game's browser takes its cue from the tags #1 Rust Server Tool has set: 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): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): The game build is 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here. 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 and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, 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. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on #1 Rust Server Tool?
A procedural map, generated by the game, is what #1 Rust Server Tool runs.
Getting in
How do you get onto #1 Rust Server Tool?
To connect, start Rust, press F1, and type client.connect 179.108.37.14:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^z,^y,^m,^p,gmvanilla,cs165217,ts8
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
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework here.
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.