On the class lists: C+ (65), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average1peak 1
Rank#3,588top 16% · #1335 in EU
Last wipe12d agoweekly schedule
Next wipe1d 1hFri 30 Oct, 11:11 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
84/ 100
B+
Holds a respectable place: #3,588 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
49/ 100
D
Needs to work on its frame rate: 30 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 466 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in wipe hold (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 16% of all ranked servers, top 46% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
···FW··
····W··
····W··
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 11:11 UTC, in 1d 1h.
Its weekly schedule tag · low confidence
usual gap7 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
1d 1hFri 30 Oct, 11:11 UTC
7d 9hThu 5 Nov, 19:00 UTCFW
8d 1hFri 6 Nov, 11:11 UTC
15d 1hFri 13 Nov, 11:11 UTC
22d 1hFri 20 Nov, 11:11 UTC
29d 1hFri 27 Nov, 11:11 UTC
35d 9hThu 3 Dec, 19:00 UTCFW
36d 1hFri 4 Dec, 11:11 UTC
The first 48 hours of its last wipes
Fri 16 OctFri 9 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 11:11 UTC12d ago
5
–
running
0
Fri 9 Oct, 10:56 UTC19d ago
1
✓ held half
7 days
0
Fri 2 Oct, 10:56 UTC26d ago
5
✓ held half
7 days
0
Thu 1 Oct, 18:57 UTCFW27d ago
5
–
0.7 days
0
Fri 25 Sep, 11:04 UTC33d ago
4
✓ held half
6.3 days
0
Fri 18 Sep, 11:05 UTC40d ago
5
✓ held half
7 days
2
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
In Europe, according to its own listing, sits #2 Omsk-Rust X10000, with the EU tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 94.137.28.90:36400 is the address to use.
How dependable is #2 Omsk-Rust X10000, and is it online at the moment?
Right now, #2 Omsk-Rust X10000 is online. According to its reported uptime, the last restart was about 35 minutes ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does #2 Omsk-Rust X10000 perform well?
It never fell below 24 server fps in the last 48 hours, averaging 30. Buildings, deployables and everything else in the world added up to as many as 68,727 entities. At its highest, it used 2,116 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does #2 Omsk-Rust X10000 sit?
The server #2 Omsk-Rust X10000 is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does #2 Omsk-Rust X10000 reset?
Its tag sets the prediction, as the record holds too few of #2 Omsk-Rust X10000's wipes to confirm its schedule. Friday 30 October at 11:11 UTC is the date set for its next wipe. The world it runs now was created 12 days 22 hours. The tags carry a weekly wipe schedule.
What happens on #2 Omsk-Rust X10000 when wipe day arrives?
The average peak on its recent wipes was 4 players. The crowd on the latest wipe was largest 4 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player numbers
Where does #2 Omsk-Rust X10000 place in the wider field of Rust servers?
In Europe, #2 Omsk-Rust X10000 is #1,335, and overall it is #3,588 on player hours over the last seven days, in the top 16% of all ranked servers.
Is #2 Omsk-Rust X10000 a busy server?
#2 Omsk-Rust X10000 is showing 0 players right now, with 100 slots in total. The seven-day average is 1 players, with a peak of 1. Over the last 48 hours, the peak hour was 04:00 UTC, averaging 0 players.
Lists and filters
What is meant by the tags on #2 Omsk-Rust X10000?
You'll see #2 Omsk-Rust X10000 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): It wipes weekly; ^i (Battlefield): Kits and high rates drive the fast PvP here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EU (Europe): You will find it under Europe in the browser in the browser, which picks them up from the server. 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 #2 Omsk-Rust X10000 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count #2 Omsk-Rust X10000 among them: Rust servers above 10x gather rate, European Rust servers, graded, Modded Rust servers, graded and Rust battlefield servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: More than 10x.
Server rules
Which rules does #2 Omsk-Rust X10000 enforce, and what are its settings?
#2 Omsk-Rust X10000 sets gather at 10000x, as its name suggests. With no change from the game default, groups take up to 8 players. It runs battlefield, kits and high rates for fast PvP. 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.
Which map is in play on #2 Omsk-Rust X10000?
A procedural map of size 3,500 and seed 253923540, generated by the game, is what #2 Omsk-Rust X10000 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto #2 Omsk-Rust X10000?
Enter client.connect 94.137.28.90:36400 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://rust-omsk.gamestores.app.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,^i,EU,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyIt wipes weekly.
Gameplay
^i
BattlefieldKits and high rates drive the fast PvP here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EU
EuropeYou will find it under Europe in the browser.
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 fair term, with more to come. Strongest in wipe hold (A+); population is the one to work on (F).