#1 Omsk-Rust X50 MAX5
Online EU 94.137.28.90:35400 checked 8m ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 69% of all ranked servers, top 88% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Monday 2 November, 11:07 UTC, in 3d 22h. Its weekly schedule tag · low confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 19 Oct, 11:07 UTC10d ago | 1 | – | running | 0 |
| Mon 12 Oct, 11:13 UTC17d ago | 2 | halved by day 6 | 7 days | 0 |
| Mon 5 Oct, 11:05 UTC24d ago | 1 | held half | 7 days | 0 |
| Thu 1 Oct, 21:14 UTC FW27d ago | 1 | held half | 3.6 days | 0 |
| Mon 28 Sep, 11:05 UTC31d ago | 2 | held half | 3.4 days | 0 |
| Mon 21 Sep, 11:06 UTC38d ago | 3 | halved by day 1 | 7 days | 0 |
| Mon 14 Sep, 11:06 UTC45d ago | 4 | halved by day 2 | 7 days | 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.
Quick answers
Population
How does #1 Omsk-Rust X50 MAX5 rank against other Rust servers?
On player hours over the last seven days #1 Omsk-Rust X50 MAX5 is #15,318, #2,558 in Europe, placing it in the top 69% of ranked servers.
How busy is #1 Omsk-Rust X50 MAX5?
Of its 100 slots, #1 Omsk-Rust X50 MAX5 is using 0 right now. A seven-day average of 0 players was counted here.
Lists and tags
What do the server tags on #1 Omsk-Rust X50 MAX5 mean?
What the game's server browser reads from #1 Omsk-Rust X50 MAX5 is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Wipes happen every week; ^i (Battlefield): High rates and kits drive fast PvP here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): This server appears under Modded because plugins or settings alter the game; EU (Europe): Its place in the server browser is under Europe. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include #1 Omsk-Rust X50 MAX5?
These Rust Population lists include #1 Omsk-Rust X50 MAX5: Rust servers with more than 10x gather, Rust servers in Europe, Modded Rust servers, counted and Rust battlefield servers. These are the filters it appears under when you browse the 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.
Wipe schedule
What does wipe day look like on #1 Omsk-Rust X50 MAX5?
The busiest point of its recent wipes averaged 1 players. Peak came 3 hours into the latest wipe. The crowd stayed above half that peak until the next wipe in 60% of its recent wipes. By day 3.5 it had fallen below half, in the cases where it did not hold.
What is the wipe schedule on #1 Omsk-Rust X50 MAX5?
The prediction follows its tag, since too few of #1 Omsk-Rust X50 MAX5's wipes are on record to confirm the schedule. A wipe is due on Monday 2 November at 11:07 UTC, the next one. Counted from 10 days 1 hours ago, that is how long the current world has stood. Its tags carry a wipe schedule of one wipe a week.
Settings
Which map does #1 Omsk-Rust X50 MAX5 run?
A procedural map of size 3,500 from seed 510244082, generated by the game, is in use on #1 Omsk-Rust X50 MAX5. The map follows from its size and seed, and RustMaps shows it from this page.
What are the rules and settings on #1 Omsk-Rust X50 MAX5?
#1 Omsk-Rust X50 MAX5 advertises a 50x gather rate in its title. No limit is set beyond the standard 8 players per group. battlefield is what it runs, kits and high rates drive fast PvP. The server browser files it under Modded, where plugins or settings alter the game. Oxide plugins are in use here. You play with Valve's anti-cheat off: VAC.
About the server
Which version of Rust does #1 Omsk-Rust X50 MAX5 run?
The setup is Rust network protocol 2634 and build 167781 on Windows for #1 Omsk-Rust X50 MAX5. Your game needs the same protocol to join; Steam takes care of updating it.
Does #1 Omsk-Rust X50 MAX5 run smoothly?
It ran at 30 server fps on average over the last 48 hours, and never went below 30. Up to 64,547 entities were present, counting buildings, deployables and everything else. The highest memory usage was 2,274 MB. Lag, as players feel it, is low fps combined with a climbing entity count.
Is #1 Omsk-Rust X50 MAX5 online, and how reliable is it?
#1 Omsk-Rust X50 MAX5 is up and running at the moment. About 9 hours ago, it restarted, according to its uptime. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.
Where is #1 Omsk-Rust X50 MAX5 located?
By its EU tag, #1 Omsk-Rust X50 MAX5 says it is in Europe. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. 94.137.28.90:35400 is where it lives.
Getting in
How do I join #1 Omsk-Rust X50 MAX5?
Open the console with F1 in Rust and enter client.connect 94.137.28.90:35400. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you. For more, visit its website: https://rust-omsk.gamestores.app.