omaga
Offline 132.255.112.233:28015 checked 18d ago
Server instruments
no direct query in 48 hoursPlayers now
20% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 588/675
- 363/525
- 49/250
- 40/250
- 130/200
- 140/300
Quick answers
from the figures on this pageWipe schedule
What wipe timing does omaga follow?
To tell the rhythm of omaga, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 18 days 15 hours ago.
Lists and filters
How should you read the tags on omaga?
Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from omaga. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does omaga appear in Rust Metrics lists and filters?
These Rust Metrics lists carry omaga: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
Where does omaga sit in the rankings?
Ranking for omaga: #13,592 on seven-day player hours, top 62% of all ranked servers.
What player count does omaga carry?
omaga is not responding; status offline, last seen 18 days 14 hours ago.
Operator and location
Where does omaga sit?
No region tag on omaga. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 132.255.112.233:28015.
What Rust version is omaga on?
Reading: omaga, Rust network protocol 2634 and build 167398, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on omaga, and is it online?
omaga reports offline. The last reading came 18 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 10 October 2026, recorded by Rust Metrics.
Settings and map
How is omaga configured, and what rules are in force?
Check: gather rate. The name omaga does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
What map is omaga on?
The game generates a procedural map for omaga.
How to join
How can you get onto omaga?
To join: start Rust, press F1 and type client.connect 132.255.112.233:28015. Or press Launch Rust here and Steam opens the game and connects you.