Omega Rust PVE Events
Offline 80.82.38.65:28015 checked 11d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 13:15 UTC, in 2d 11h. Its weekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 2d 11h | Fri 30 Oct, 13:15 UTC | its own |
| 8d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 9d 11h | Fri 6 Nov, 13:15 UTC | its own |
| 16d 11h | Fri 13 Nov, 13:15 UTC | its own |
| 23d 11h | Fri 20 Nov, 13:15 UTC | its own |
| 30d 11h | Fri 27 Nov, 13:15 UTC | its own |
| 36d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 37d 11h | Fri 4 Dec, 13:15 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 13:15 UTC11d ago | 3 | – | running | 3 |
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
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| [PvE] TruePvE [x1-x5|Loot+|NPC|RB|Quests|NoRaid/NoKill] | groups of 200+ · 1x · weekly · 14 on average | 4 / 100 |
| #3 Wasilisc PvE х5 | EU · groups of 8+ · weekly · 9 on average | 1 / 200 |
| RustMode PvE | 10/22 | No Tech Tree | Skills | Raids | Events | NA · groups of 150+ · weekly · 5 on average | 0 / 50 |
| TRINUM.RU PVE NoKill NoRaid Skills Artifacts Boss Zombie | EU · groups of 8+ · weekly · 4 on average | 2 / 250 |
| Moradon - PVE - [AU] [Raidable Bases] [Skill Tree] | OC · groups of 8+ · weekly · 4 on average | 0 / 30 |
| [US] Northnet 1x PVE | Events | Raids | No Tech Tree | Custom W | NA · groups of 8+ · 1x · weekly · 2 on average | 0 / 75 |
Quick answers
from the figures on this pageWipe data
When does Omega Rust PVE Events wipe?
The prediction follows its tag, because too few of Omega Rust PVE Events's wipes are on record to confirm the schedule. Friday 30 October at 13:15 UTC is the date the next wipe falls on. The world now in play was created 11 days 11 hours ago. The tags list a wipe schedule of one week.
Wipe day on Omega Rust PVE Events: what should you expect?
Recent wipes averaged a busiest count of 3 players. The highest player count on the latest wipe arrived 0 hours in.
Server details
What is the hosting location of Omega Rust PVE Events?
No region appears in what Omega Rust PVE Events publishes. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 80.82.38.65:28015 is its address.
Which Rust version is Omega Rust PVE Events on?
Rust network protocol 2634 and build 166494 on Windows is the setup for Omega Rust PVE Events. Joining requires the same protocol on your game; Steam handles the update.
What uptime does Omega Rust PVE Events show, and is it up?
Last seen 11 days 11 hours ago, Omega Rust PVE Events now reports offline. Of 168 hours in the last 7 full days, 0 were up: 0%. The first sighting of it by Rust Server Analytics was on 4 October 2026.
Tags
How should the tags on Omega Rust PVE Events be read?
Tags from Omega Rust PVE Events, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default team size of 8; v2634 (Protocol): To join, your game version must match protocol 2634; cs166494 (Build): Build number 166494; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^w (Weekly): Wipes run on a weekly cycle; ^p (PvE): The threat comes from the world, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature Omega Rust PVE Events?
These Rust Server Analytics lists include Omega Rust PVE Events: Modded Rust servers: live data and PvE Rust servers by live population. On the server list, the filters that return it are: Type: Modded; Game mode: PvE; Server tag: Weekly ^w, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Population
What position does Omega Rust PVE Events hold in the server rankings?
The seven-day player-hours rank for Omega Rust PVE Events is #12,920, inside the top 60% of all ranked servers.
How many players does Omega Rust PVE Events carry?
No response from Omega Rust PVE Events at the latest check, with a last sighting 11 days 11 hours ago.
Settings
How is Omega Rust PVE Events configured, and what rules apply?
Gather rate is not mentioned in the name of Omega Rust PVE Events. The default group cap of 8 players applies. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.
The map on Omega Rust PVE Events: which one is it?
A procedural map of size 3,500 with seed 9524314, generated by the game, runs on Omega Rust PVE Events. The map is reproducible from its size and seed and can be seen on RustMaps from here. Named map: Custom Map.
How to join
What is the way onto Omega Rust PVE Events?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 80.82.38.65:28015.