Rust Server TrendsSeismic network · station log
Recording Stations11,700 Players38,808 Active2,943 Wipes · 3 h91 48 h

Station XX-12920 · no signal

Omega Rust PVE Events

Offline 80.82.38.65:28015 checked 12d ago

weekly wipes moddedoxidepve
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,920
top 60%
Last wipe
12d ago
weekly schedule
Next wipe
1d 10h
Fri 30 Oct, 13:15 UTC
Seismic record · station XX-12920 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct8 Oct12 Oct15 Oct19 Oct23 Oct

Top 60% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 13:15 UTC, in 1d 10h. Its weekly schedule tag · low confidence

wipe-day peak
3players, last three wipes

Coming wipes

  1. 1d 10hFri 30 Oct, 13:15 UTC
  2. 7d 16hThu 5 Nov, 19:00 UTCFW
  3. 8d 10hFri 6 Nov, 13:15 UTC
  4. 15d 10hFri 13 Nov, 13:15 UTC
  5. 22d 10hFri 20 Nov, 13:15 UTC
  6. 29d 10hFri 27 Nov, 13:15 UTC
  7. 35d 16hThu 3 Dec, 19:00 UTCFW
  8. 36d 10hFri 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 13:15 UTC12d ago M0.0steady 3 – – running 3

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[PvE] TruePvE [x1-x5|Loot+|NPC|RB|Quests|NoRaid/NoKill] groups of 200+ · 1x · weekly · 13 on average
3/ 100
#3 Wasilisc PvE х5 EU · groups of 8+ · weekly · 9 on average
1/ 200
[SEA]Singapore PVEx20 10/23/26 SkillTree Events EA · groups of 8+ · weekly · 6 on average
2/ 50
RustMode PvE | 10/22 | No Tech Tree | Skills | Raids | Events NA · groups of 150+ · weekly · 4 on average
1/ 50
Moradon - PVE - [AU] [Raidable Bases] [Skill Tree] OC · groups of 8+ · weekly · 4 on average
0/ 30
TRINUM.RU PVE NoKill NoRaid Skills Artifacts Boss Zombie EU · groups of 8+ · weekly · 4 on average
0/ 250
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Omega Rust PVE Events?

Generated by the game, the map on Omega Rust PVE Events is procedural, size 3,500 with seed 9524314. You can view it on RustMaps from this page: the same size and seed produce the same map. You will find the map named Custom Map.

Which settings and rules apply on Omega Rust PVE Events?

No gather rate appears in the name of Omega Rust PVE Events. Groups hold up to 8 players, which is the default for the game. pve is the game mode, no player-versus-player fighting. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Omega Rust PVE Events right now?

A reading taken now finds Omega Rust PVE Events offline; the most recent activity was 12 days 12 hours ago.

How does Omega Rust PVE Events rank against other Rust servers?

On player hours for the past week, Omega Rust PVE Events sits at #12,920, which puts it inside the top 60% of every ranked server.

Server details

How reliably does Omega Rust PVE Events stay online?

No contact with Omega Rust PVE Events right now, and the last recorded contact was 12 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 4 October 2026.

Which region does Omega Rust PVE Events run from?

No region is published by Omega Rust PVE Events. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 80.82.38.65:28015.

What build of Rust does Omega Rust PVE Events use?

On Windows, Omega Rust PVE Events runs Rust network protocol 2634 and build 166494. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Omega Rust PVE Events?

The recent wipes averaged a busiest count of 3 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does Omega Rust PVE Events wipe, and on which days?

The prediction follows its tag, because too few of Omega Rust PVE Events's wipes are on record to confirm its schedule. The date of its next wipe is Friday 30 October at 13:15 UTC. The present world dates from 12 days 12 hours. Its tags state a weekly wipe schedule.

Tags

What do the server tags on Omega Rust PVE Events mean?

These are the tags Omega Rust PVE Events publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^w (Weekly): Wipes happen weekly; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Omega Rust PVE Events appear?

You will find Omega Rust PVE Events on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters 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.

How to join

What steps get you onto Omega Rust PVE Events?

To join, enter client.connect 80.82.38.65:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^w,^p,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166494
Build Game build: 166494.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Wipe schedule

^w
Weekly Wipes happen weekly.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.