RUST METRICSFlight deck · live data
Data live Servers11,673 Players46,970 Populated2,995 Fresh wipes 3 h95 Scan5 min
‹ All servers82.215.64.19:28015
Offline Full Queue Fresh wipe Wipe due No query

OT Events

Offline 82.215.64.19:28015 checked 23d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,983top 71%
Last wipe54d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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 17 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 Sep25 Sep29 Sep4 Oct8 Oct13 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

What wipe timing does OT Events follow?

The rhythm of OT Events's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 54 days 22 hours ago the current world was made.

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): The game mode is plain Rust survival; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the 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?

Rust Metrics lists featuring OT Events: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does OT Events hold among Rust servers?

Ranking for OT Events: #15,983 on seven-day player hours, top 71% of all ranked servers.

What is the population on OT Events?

Reading for OT Events: offline at this moment; last seen 23 days 6 hours ago.

Server

Which location does OT Events run from?

Reading: location. OT Events gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 82.215.64.19:28015.

What Rust version is OT Events on?

Reading: OT Events, Rust network protocol 2633 and build 165217, Linux. Matching protocol is required to join. Let Steam update your game.

What is the uptime on OT Events, and is it online?

OT Events reports offline. The last reading came 23 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name OT Events does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is OT Events on?

Check: map. Procedural, size 4,250, seed 1337, generated by the game on OT Events. View it on RustMaps from this page: matching size and seed give an identical map. Read the map name: Custom Map.

How to join

How do you connect to OT Events?

Press F1 in Rust and enter client.connect 82.215.64.19:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://oilteam.gg/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players The server holds 0 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.