RUST METRICSFlight deck · live data
Data live Servers11,880 Players98,236 Populated3,914 Fresh wipes 3 h395 Scan5 min
‹ All servers82.215.64.19:28021
Online Full Queue Fresh wipe Wipe due No query

OT Events

Online 82.215.64.19:28021 checked 8m ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

no slots published 7-day avg7-day peak 82, 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 20 40 60 80 ENT 47,251 ×1000

Entities

48 h range 46,202–48,489 · memory 3,328 MB
1239 ET SINCE RESTART 1D 17H

Uptime

1 days 17 hours since its last restart, at the last reading
7-day average3peak 82
Rank#1,764top 8%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Memory3,328MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75117:0002:0011:0021:0006:0015:00Wiped Tue 27 Oct, 20:15 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
01020304017:0002:0011:0021:0006:0015:00Wiped Tue 27 Oct, 20:15 UTCWIPE

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 24 Sep. 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 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap6.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak55players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Sat 24 OctFri 23 OctWed 14 Oct
0255075100+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 82, 4 hours in, with 1 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 20:15 UTC1d ago – – running 1
Sat 24 Oct, 12:43 UTC5d ago 82+1 queue halved by day 1 3.3 days 0
Fri 23 Oct, 19:59 UTC5d ago 82+1 queue – 0.7 days 0
Wed 14 Oct, 14:04 UTC15d ago 0 – 9.2 days 0
Thu 24 Sep, 03:14 UTC35d ago 1 halved by day 1 20.5 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.

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 happens on OT Events when wipe day comes?

The busiest point of its recent wipes drew 55 players on average. 4 hours after the wipe the crowd peaked on the latest wipe, with 1 more in the queue. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 1 it fell below half when it didn't.

How often does OT Events wipe, and when?

No next wipe can be predicted for OT Events, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 hours ago the current world was made.

Lists and filters

Which tags does OT Events carry, and what do they mean?

These are the tags OT Events publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): 0 slots in total; ts100 (Group limit): You may team up with at most 100; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does OT Events appear in Rust Metrics lists and filters?

On Rust Metrics, OT Events sits in these lists: 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 3 days.

Player count

What position does OT Events hold among Rust servers?

Ranking for OT Events: #1,764 on seven-day player hours, top 8% of all ranked servers.

How full does OT Events get?

0 players are on OT Events at this moment. Check: players over seven days. Average 3, peak 82. Average at the busiest hour was 1 players, at 19:00 UTC over the last 48 hours.

Server

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. Check: address. It reads 82.215.64.19:28021.

What Rust version is OT Events on?

Reading: OT Events, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is performance on OT Events within range?

Check: fps. Average 40 server fps over the last 48 hours, low of 40. Within range. Peak entity count: 48,489. Buildings, deployables and all else included. Reading: 3,904 MB of memory at the highest. Expect lag when fps falls and entities climb.

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

Check: connection. OT Events is online at this moment. By its reported uptime, the last restart was roughly 41 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does OT Events enforce, and what are its settings?

Check: gather rate. The name OT Events does not state one. Check: group limit. Up to 100 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on OT Events?

From seed 1337, the game generates the procedural map on OT Events. Its size is 5,000. 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?

Check: join. Open Rust, press F1, then enter client.connect 82.215.64.19:28021. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players 0 slots in total.
ts100
Group limit You may team up with at most 100.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock 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.