Working its way up from the back of the class: #14,373 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
36/ 100
F
Slipped a little: down 4,061 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 tag appears for ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕, but the name suggests Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 178.173.127.163:28015.
How reliable is ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕, and is it up?
At this moment, ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ is offline; the last time it was seen was 33 days 3 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 26 September 2026.
On what Rust version does ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ sit?
Rust network protocol 2633 and build 165217 on Windows is what ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ wipe, and how often?
The record holds too few of ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 33 days 7 hours.
Player numbers
Where does ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ sit among Rust servers?
Over the last seven days, ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ has #14,373 for player hours, in the top 61% of all ranked servers.
How many players does ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ usually have?
╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ is offline at the moment; the last time it was seen was 33 days 3 hours ago.
Tags
How should you read the tags on ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): Its slot count is 500; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ 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 ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ appear in the Rust Server Score lists and filters?
These Rust Server Score lists count ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ among them: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ set up, and what rules does it keep?
Nothing in the name of ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. VAC, Valve's anti-cheat, is not enabled.
╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ runs which map?
╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕ runs a procedural map, which the game generates.
How to join
How should you connect to ╨Ь╨╛╨╣ ╨┐╨╕╤А╨░╤В╤Б╨║╨╕?
To connect, start Rust, press F1, and type client.connect 178.173.127.163:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max playersIts slot count is 500.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from F to F.