Rust Data

rustdata.spaceservers80.82.38.65:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 80.82.38.65:28015 checked 11d ago

Omega Rust PVE Events

weekly wipes moddedoxidepve

Connect

srv = rust.server("80.82.38.65:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #12,920 # top 60%
last wipe 11d ago # weekly schedule
next wipe 2d 1h # Fri 30 Oct, 13:15 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

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

wipe-day peak3players, last three wipes

Coming wipes

inatkind
02d 1hFri 30 Oct, 13:15 UTCwipe
18d 7hThu 5 Nov, 19:00 UTCFW force wipe
29d 1hFri 6 Nov, 13:15 UTCwipe
316d 1hFri 13 Nov, 13:15 UTCwipe
423d 1hFri 20 Nov, 13:15 UTCwipe
530d 1hFri 27 Nov, 13:15 UTCwipe
636d 7hThu 3 Dec, 19:00 UTCFW force wipe
737d 1hFri 4 Dec, 13:15 UTCwipe

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 16 Oct, 13:15 UTC11d ago 3 NaN 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.

display(srv.map, srv.info())

Map

3500 · seed 9524314
Map of Omega Rust PVE Events
map
Custom Map
size
3500
seed
9524314

Server

srv.info()
address
80.82.38.65:28015
region
–
max players
50
group limit
8, the default
wipe schedule
weekly
last wipe
16 Oct 2026, 13:24 UTC
hostname
–
first seen
4 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[PvE] TruePvE [x1-x5|Loot+|NPC|RB|Quests|NoRaid/NoKill]groups of 200+ · 1x · weekly · 14 on average9/100
1#3 Wasilisc PvE х5EU · groups of 8+ · weekly · 9 on average12/200
2[SEA]Singapore PVEx20 10/23/26 SkillTree EventsEA · groups of 8+ · weekly · 6 on average5/50
3Moradon - PVE - [AU] [Raidable Bases] [Skill Tree]OC · groups of 8+ · weekly · 4 on average0/30
4TRINUM.RU PVE NoKill NoRaid Skills Artifacts Boss ZombieEU · groups of 8+ · weekly · 4 on average5/250
5[US] Northnet 1x PVE | Events | Raids | No Tech Tree | Custom WNA · groups of 8+ · 1x · weekly · 2 on average0/75

Quick answers

From the figures on this page.

Population

What position does Omega Rust PVE Events take in the server rankings?

Player hours over seven days put Omega Rust PVE Events at #12,920, in the top 60% of the ranked set.

What population does Omega Rust PVE Events carry?

The current row shows Omega Rust PVE Events offline; the last response was 11 days 21 hours ago.

About the server

Which Rust version is Omega Rust PVE Events on?

Version Rust network protocol 2634 and build 166494 on Windows is reported by Omega Rust PVE Events. The protocol has to match before you can join, and Steam does the updating.

How reliable is Omega Rust PVE Events, and is it up?

Omega Rust PVE Events is offline at this refresh; the last response came 11 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 4 October 2026.

Where does Omega Rust PVE Events sit?

For Omega Rust PVE Events, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 80.82.38.65:28015.

Rules, settings, map

Which settings and rules does Omega Rust PVE Events run?

The name Omega Rust PVE Events carries no gather rate. Eight players per group: that is the game's default, and it applies here. pve is the game mode here, and player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

Which map has Omega Rust PVE Events loaded?

Omega Rust PVE Events runs a procedural map of size 3,500 with seed 9524314, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.

Wipe schedule

When does Omega Rust PVE Events wipe, and on what schedule?

The prediction follows the tag, because Omega Rust PVE Events's wipes on record are too few to confirm the schedule. On Friday 30 October at 13:15 UTC the next wipe is due. This world was created 11 days 22 hours ago. Its tags carry a weekly wipe schedule.

What is wipe day on Omega Rust PVE Events like?

The average peak over recent wipes is 3 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain Omega Rust PVE Events?

These Rust Data lists include Omega Rust PVE Events: Modded Rust servers and Rust PvE servers. 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.

How should you read the server tags on Omega Rust PVE Events?

These tags are published by Omega Rust PVE Events and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Build number: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^w (Weekly): The interval is one week; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way into Omega Rust PVE Events?

Enter client.connect 80.82.38.65:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166494
Build Build number: 166494.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^w
Weekly The interval is one week.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins 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.

Rust Data 63,966 players 11,688 servers online