Online EU 94.137.28.90:36400 checked 9m ago
#2 Omsk-Rust X10000
Connect
srv = rust.server("94.137.28.90:36403")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 16% of all ranked servers, top 46% in EU. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Friday 30 October, 11:11 UTC, in 20h. # Its weekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 20h | Fri 30 Oct, 11:11 UTC | wipe |
| 1 | 7d 4h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 7d 20h | Fri 6 Nov, 11:11 UTC | wipe |
| 3 | 14d 20h | Fri 13 Nov, 11:11 UTC | wipe |
| 4 | 21d 20h | Fri 20 Nov, 11:11 UTC | wipe |
| 5 | 28d 20h | Fri 27 Nov, 11:11 UTC | wipe |
| 6 | 35d 4h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 35d 20h | Fri 4 Dec, 11:11 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 4 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 11:11 UTC13d ago | 5 | NaN | running | 0 |
| 1 | Fri 9 Oct, 10:56 UTC20d ago | 1 | held half | 7 days | 0 |
| 2 | Fri 2 Oct, 10:56 UTC27d ago | 5 | held half | 7 days | 0 |
| 3 | Thu 1 Oct, 18:57 UTC FW27d ago | 5 | NaN | 0.7 days | 0 |
| 4 | Fri 25 Sep, 11:04 UTC34d ago | 4 | held half | 6.3 days | 0 |
| 5 | Fri 18 Sep, 11:05 UTC41d 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.
display(srv.map, srv.info())Map
3500 · seed 253923540
- map
- Procedural Map
- size
- 3500
- seed
- 253923540
Server
srv.info()- address
- 94.137.28.90:36400
- region
- EU
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 16 Oct 2026, 11:11 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANS | EU · groups of 100+ · 1000x · weekly · 63 on average | 128/150 |
| 1 | X1000000|ONLYPVP|X1000000000000000000|FUN|FPS++ | EU · groups of 8+ · 1e+06x · weekly · 10 on average | 27/200 |
| 2 | KRISTALIX RUST - X50 | NOLIMIT | 27.10 | EU · groups of 30+ · 50x · weekly · 8 on average | 8/150 |
| 3 | EU|AndysolAM 20x No BPs|PVP|Shop|Loot+|Kits|Raid+|MyMini|Skinbo | EU · groups of 10+ · 20x · weekly · 6 on average | 12/200 |
| 4 | PERFECT RUST X1000 NOLIMIT SHOP LOOT+ FPS+ | EU · groups of 25+ · 1000x · weekly · 5 on average | 14/250 |
| 5 | #1 DARKNESS X1000000 | BATTLEFIELD | PVP | KITS | TP | WP29.10 | EU · groups of 50+ · 1e+06x · weekly · 4 on average | 4/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does #2 Omsk-Rust X10000 rank?
On seven-day player hours #2 Omsk-Rust X10000 is #3,635 overall and #1,345 in Europe, inside the top 16% of all ranked servers.
What population does #2 Omsk-Rust X10000 carry?
The sample now reads 0 players for #2 Omsk-Rust X10000, out of 100 slots. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 04:00 UTC, averaging 0 players.
Server facts
How well does #2 Omsk-Rust X10000 perform?
Averaged over 48 hours: 30 server fps, never under 24. Entity numbers reached 68,727, and that includes buildings, deployables and the rest. Memory peaked at 2,116 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on #2 Omsk-Rust X10000?
The build is Rust network protocol 2634 and build 167781 on Windows, run by #2 Omsk-Rust X10000. Steam updates your game for you, but the protocol must match to join.
Is #2 Omsk-Rust X10000 up, and what does its uptime show?
#2 Omsk-Rust X10000 reports itself online at the current refresh. Count back 22 minutes from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.
In which location is #2 Omsk-Rust X10000 hosted?
The EU tag is what #2 Omsk-Rust X10000 uses to list itself in Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 94.137.28.90:36400 is its address.
Map and rules
Which rules apply on #2 Omsk-Rust X10000, and what settings?
Gather sits at 10000x, read from the server's own name: #2 Omsk-Rust X10000. Eight players per group: that is the game's default, and it applies here. Game mode battlefield, with this note: fast PvP, kits supplied, rates high. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has #2 Omsk-Rust X10000 selected?
The game generates the map on #2 Omsk-Rust X10000: procedural, size 3,500, seed 253923540. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does #2 Omsk-Rust X10000 wipe, and on what schedule?
Too few wipes are on record for #2 Omsk-Rust X10000 to confirm its schedule, so the tag drives the prediction. Friday 30 October at 11:11 UTC is when the next wipe is due. This world was created 13 days 3 hours ago. Its tags carry a weekly wipe schedule.
On #2 Omsk-Rust X10000, what happens on wipe day?
The average peak over recent wipes is 4 players. The crowd on the latest wipe topped out 4 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Where does #2 Omsk-Rust X10000 appear among Rust Data lists and filters?
The Rust Data lists that #2 Omsk-Rust X10000 fits are: EU Rust servers, Modded Rust servers, Rust servers with more than 10x and Rust battlefield servers. These filters bring it up 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.
How should you read the server tags on #2 Omsk-Rust X10000?
Read by the game's server browser, the tags #2 Omsk-Rust X10000 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^w (Weekly): A wipe every week; ^i (Battlefield): High rates and kits, for fast PvP; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; EU (Europe): The server browser files it under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join #2 Omsk-Rust X10000?
Enter client.connect 94.137.28.90:36400 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://rust-omsk.gamestores.app.