RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,471 Populated3,963 Fresh wipes 3 h334 Scan5 min
‹ All servers82.215.64.19:28018
Online Full Queue Fresh wipe Wipe due No query

OT Events

Online 82.215.64.19:28018 checked 10m ago

moddedoxide
COM 1 · connect

Server instruments

last reading Thu 16:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg7-day peak 72, past the slots
0 10 30 60 120 256 FPS 40 SERVER FPS

Server fps

48 h low 40 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 59 ×1000

Entities

48 h range 59–59 · memory 2,290 MB
1239 ET SINCE RESTART 5D 02H

Uptime

5 days 2 hours since its last restart, at the last reading
7-day average0peak 72
Rank#4,422top 20%
Last wipe5d agono schedule published
Next wipe–too few wipes seen yet
Memory2,290MBat the last reading
REC 1

Players

AveragePeak
0123419:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304019:0004:0013:0022:0007:0016:00

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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep27 Sep23 Oct26 Oct29 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak72players, last three wipes

The first 48 hours of its last wipes

010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 72, 22 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 20:44 UTC5d ago 72 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on OT Events?

At their busiest, its recent wipes drew 72 players on average. After the latest wipe, numbers topped out at 22 hours.

What wipe timing does OT Events follow?

The rhythm of OT Events's wipes cannot be told yet: too few 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 in play was created 5 days 21 hours ago.

Tags

How should you read the tags on OT Events?

These are the tags OT Events publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): Slots: 0; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show OT Events?

These Rust Metrics lists carry OT Events: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Player count

Where does OT Events sit in the rankings?

Player hours over seven days put OT Events at #4,422, in the top 20% of all ranked servers.

What player count does OT Events carry?

Reading for OT Events: 0 players online now. Check: players over seven days. Average 0, peak 72.

Operator and location

Which location does OT Events run from?

No region tag on OT Events. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 82.215.64.19:28018.

What Rust version is OT Events on?

Reading: OT Events, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on OT Events within range?

Over the last 48 hours the average was 40 server fps; the floor was 40. Check: entities. The peak was 59, counting buildings, deployables and the rest of the world. Memory peak: 2,294 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is OT Events, and is it online now?

OT Events reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 5 days 2 hours ago. Uptime for the last 7 full days: 123 of 168 hours, or 73%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

How is OT Events configured, and what rules are in force?

No gather rate appears in the name: OT Events. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on OT Events?

Check: map. Procedural, size 5,000, seed 1337, generated by the game on OT Events. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Map name, as listed: Custom Map.

Join

How do you connect to OT Events?

Press F1 in Rust and enter client.connect 82.215.64.19:28018. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players Slots: 0.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.