Working its way up from the back of the class: #15,366 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
52/ 100
D
Moving up: up 611 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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 71% 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
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 13 Oct, 12:22 UTC15d ago
0
–
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
:thinking: 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 203.94.34.210:28020.
How reliable is :thinking:, and is it up?
At this moment, :thinking: is offline; the last time it was seen was 15 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 6 October 2026, Rust Server Score saw it for the first time.
Which Rust version is :thinking: running?
Rust network protocol 2634 and build 167781 on Windows is what :thinking: runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does :thinking: wipe its map?
There are too few wipes on record for :thinking: to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 15 days 23 hours have passed since this world was made.
What should you expect from wipe day on :thinking:?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does :thinking: sit among Rust servers?
Over the last seven days, :thinking: has #15,366 for player hours, in the top 71% of all ranked servers.
Is :thinking: a busy server?
:thinking: is offline at the moment; the last time it was seen was 15 days 23 hours ago.
Lists and filters
What do :thinking:'s tags stand for?
You'll see :thinking: tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): Its slot count is 200; ts90 (Group limit): No team may go above 90; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^e (Minigames): It hosts minigames such as arenas, Bedwars and parkour; ^d (Combat training): The loot comes to you: practise your aim and PvP here; ^o (Oxide): Plugin framework: 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 Rust Server Score filters and lists feature :thinking:?
Rust Server Score lists that include :thinking:: Modded Rust servers, graded and Rust combat training servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Minigames ^e, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is :thinking: set up, and what rules does it keep?
Nothing in the name of :thinking: states a gather rate. The limit for a group is 90 players. You get minigames & battle royale here, parkour, arenas, battle royale and Bedwars. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Connecting
How should you connect to :thinking:?
To connect, start Rust, press F1, and type client.connect 203.94.34.210:28020. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^e,^d,gmrust,cs167781,ts90,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max playersIts slot count is 200.
ts90
Group limitNo team may go above 90.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Gameplay
^e
MinigamesIt hosts minigames such as arenas, Bedwars and parkour.
^d
Combat trainingThe loot comes to you: practise your aim and PvP here.
Mods and access
^o
OxidePlugin framework: 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. Strongest in momentum (D); standing is the one to work on (F).