Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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 Wednesday 4 November, 03:24 UTC, in 5d 18h.
Weekly: 7 days after its last 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 RU HUQQA MOSCOW, but the name suggests Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 157.85.91.127:26453.
How dependable is RU HUQQA MOSCOW, and is it online at the moment?
You cannot join now: RU HUQQA MOSCOW is offline, last seen 45 days ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does RU HUQQA MOSCOW sit?
Rust network protocol 2632 and build 161125 on Linux is what RU HUQQA MOSCOW runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does RU HUQQA MOSCOW wipe, and how often?
weekly: 7 days after its last wipe gives the basis for estimating RU HUQQA MOSCOW's next wipe. It is due to wipe next on Wednesday 4 November at 03:24 UTC. The world it runs now was created 71 days 5 hours. Wipes are scheduled weekly, according to its tags.
Player count
Where does RU HUQQA MOSCOW place in the wider field of Rust servers?
Over the last seven days, RU HUQQA MOSCOW has #15,104 for player hours, in the top – of all ranked servers.
How many players does RU HUQQA MOSCOW usually have?
The last sighting of RU HUQQA MOSCOW was 45 days ago, and it is offline right now.
Tags and filters
What is meant by the tags on RU HUQQA MOSCOW?
The game's browser takes its cue from the tags RU HUQQA MOSCOW has set: gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): 40 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): To get in, your game needs to be on the same version: the protocol is 2632; cs161125 (Build): Build number: 161125; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 RU HUQQA MOSCOW appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RU HUQQA MOSCOW among them: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Map and rules
Which rules does RU HUQQA MOSCOW enforce, and what are its settings?
You will find no gather rate in the name of RU HUQQA MOSCOW. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
RU HUQQA MOSCOW runs which map?
The game generates a procedural map for RU HUQQA MOSCOW.
Getting in
How should you connect to RU HUQQA MOSCOW?
Enter client.connect 157.85.91.127:26453 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 asmp40,ptrak,$r?,v2632,^w,^v,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max players40 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolTo get in, your game needs to be on the same version: the protocol is 2632.
cs161125
BuildBuild number: 161125.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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.
Not enough figures yet to write a report. Check back after a few days on the list.