Working its way up from the back of the class: #15,991 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
17/ 100
F
Lost ground: down 10,703 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
···F··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 Sunday 1 November, 16:15 UTC, in 4d 16h.
Its weekly schedule tag · low confidence
usual gap2.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 3
Coming wipes
4d 16hSun 1 Nov, 16:15 UTC
8d 18hThu 5 Nov, 19:00 UTCFW
11d 16hSun 8 Nov, 16:15 UTC
18d 16hSun 15 Nov, 16:15 UTC
25d 16hSun 22 Nov, 16:15 UTC
32d 16hSun 29 Nov, 16:15 UTC
36d 18hThu 3 Dec, 19:00 UTCFW
39d 16hSun 6 Dec, 16:15 UTC
The first 48 hours of its last wipes
Sun 4 OctThu 1 OctFri 25 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 16:15 UTC23d ago
0
–
running
0
Thu 1 Oct, 19:16 UTCFW26d ago
4
–
2.9 days
1
Fri 25 Sep, 09:00 UTC32d ago
3
halved by day 3
6.4 days
0
Thu 24 Sep, 15:16 UTC33d ago
3
–
0.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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Omega Rust PVE Events leaves the region unpublished. 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.
Is Omega Rust PVE Events up, and how steady is its uptime?
The server is down: Omega Rust PVE Events is offline now, with the last sighting 23 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 24 September 2026.
Which Rust version is Omega Rust PVE Events running?
The server Omega Rust PVE Events is on Rust network protocol 2634 and build 166494 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Omega Rust PVE Events wipe, and how often?
The prediction follows its tag, because too few of Omega Rust PVE Events's wipes are on record to confirm the schedule. It is due to wipe next on Sunday 1 November at 16:15 UTC. 23 days 7 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on Omega Rust PVE Events?
The average peak on its recent wipes was 2 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 3.
Player numbers
What position does Omega Rust PVE Events hold in the rankings?
In the top 71% of all ranked servers, Omega Rust PVE Events sits at #15,991 for player hours over the last seven days.
How many players does Omega Rust PVE Events usually have?
Omega Rust PVE Events is offline at the moment; the last time it was seen was 23 days 7 hours ago.
Lists and filters
What do Omega Rust PVE Events's tags stand for?
The game's browser takes its cue from the tags Omega Rust PVE Events has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): The game build is 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show 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.
Map and 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 group limit stays at the game's default of 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Omega Rust PVE Events runs which map?
A procedural map, generated by the game, is what Omega Rust PVE Events runs.
How to join
How should you connect to Omega Rust PVE Events?
To connect, start Rust, press F1, and type client.connect 80.82.38.65:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^p,^w,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under 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. Strongest in standing (F); wipes are the one to work on (F).