Working its way up from the back of the class: #12,920 on player hours.
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
37/ 100
F
Slipped a little: down 3,369 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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
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.
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····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, 13:15 UTC, in 2d 4h.
Its weekly schedule tag · low confidence
wipe-day peak3players, last three wipes
Coming wipes
2d 4hFri 30 Oct, 13:15 UTC
8d 10hThu 5 Nov, 19:00 UTCFW
9d 4hFri 6 Nov, 13:15 UTC
16d 4hFri 13 Nov, 13:15 UTC
23d 4hFri 20 Nov, 13:15 UTC
30d 4hFri 27 Nov, 13:15 UTC
36d 10hThu 3 Dec, 19:00 UTCFW
37d 4hFri 4 Dec, 13:15 UTC
The first 48 hours of its last wipes
No hourly players around its wipes yet.
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
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Omega Rust PVE Events. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 80.82.38.65:28015.
How reliable is Omega Rust PVE Events, and is it up?
You cannot join now: Omega Rust PVE Events is offline, last seen 11 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 4 October 2026, Rust Server Score saw it for the first time.
What Rust version is Omega Rust PVE Events on?
Rust network protocol 2634 and build 166494 on Windows is what Omega Rust PVE Events runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Omega Rust PVE Events wipe its map?
Its tag sets the prediction, as the record holds too few of Omega Rust PVE Events's wipes to confirm its schedule. Expect the next wipe on Friday 30 October at 13:15 UTC. It has been running its current world for 11 days 19 hours. Wipes are scheduled weekly, according to its tags.
What happens on Omega Rust PVE Events when wipe day arrives?
The average peak on its recent wipes was 3 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does Omega Rust PVE Events place in the wider field of Rust servers?
Over the last seven days, Omega Rust PVE Events has #12,920 for player hours, in the top 60% of all ranked servers.
What does the population on Omega Rust PVE Events look like?
Omega Rust PVE Events is offline at the moment; the last time it was seen was 11 days 19 hours ago.
Tags
What is meant by the tags on Omega Rust PVE Events?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Omega Rust PVE Events publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Omega Rust PVE Events?
These Rust Server Score lists count Omega Rust PVE Events among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: 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.
Server rules
Which rules does Omega Rust PVE Events enforce, and what are its settings?
You will find no gather rate in the name of Omega Rust PVE Events. The default of 8 players applies as the group cap. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Omega Rust PVE Events?
A procedural map of size 3,500 and seed 9524314, generated by the game, is what Omega Rust PVE Events runs. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Connecting
How should you connect to Omega Rust PVE Events?
Enter client.connect 80.82.38.65:28015 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 asmp50,ptrak,$r?,v2634,^w,^p,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Even marks across the subjects, from F to F.