StatusLive Servers online11,835 Players94,909 Populated3,850 Wiped · 3 h528 Interval5 min Date29 OCT 2026

DWG RG-S1756Server sheetchecked 9m ago

OT Events

Online 82.215.64.19:28021 checked 9m ago

moddedoxide
Connect
Players now 0/ ?
7-day average3peak 82
Rank#1,756top 8%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75121:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Fig. 1Players on OT Events
Fig. 2

Server performance

01020304021:0006:0015:0001:0010:0019: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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 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.

Fig. 3Rank on player hours, daily
Schedule

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 20:15 UTC2d 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 UTC6d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 151 on average
78 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
135 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
131 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average
42 / 700
05
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average
135 / 700
06
RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average
347 / 350
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for OT Events, and is it up?

OT Events is up at this moment. The uptime it reports puts the last restart at about 45 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.

Is OT Events stable in the figures recorded?

Average server fps over the last 48 hours is 40; the lowest was 40. Counted at its highest: 47,430 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,643 MB. What players feel as lag is low fps together with a climbing entity count.

In which location is OT Events hosted?

There is no region published by OT Events. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 82.215.64.19:28021 is its address.

On which Rust version is OT Events running?

On Linux, OT Events runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on OT Events?

Current player count on OT Events: 0. The seven-day mean is 3 players; the peak over the same period is 82. The 48-hour peak falls at 21:00 UTC, averaging 1 players.

In the rankings, which position does OT Events hold?

Within the top 8% of all ranked servers: OT Events at #1,756 for player hours, seven days recorded.

Wipe data

On OT Events, what does the data show for wipe day?

At their busiest, its recent wipes drew 55 players on average. 4 hours after the latest wipe the crowd peaked, with 1 further players waiting in the queue. Half that peak was held until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 1.

Which times and days are wipes plotted at on OT Events?

OT Events wipes at times that follow no pattern, so no next wipe can be predicted. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 47 hours ago the current world was made.

Settings

What settings and rules apply on OT Events?

The name of OT Events records no gather rate. The group limit is 100 players. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.

On which map is OT Events played?

Size 5,000 with seed 1337: that is the procedural map OT Events runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.

Filters

On Rust Graphs, which lists and filters contain OT Events?

These Rust Graphs lists include OT Events: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meaning is attached to each tag on OT Events?

The game's server browser reads these tags from OT Events: gmrust (Game mode): Standard survival, as Rust plays; mp0 (Max players): The slot count is 0; ts100 (Group limit): Teams hold no more than 100; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

What is the way to connect to OT Events?

Connect with client.connect 82.215.64.19:28021: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp0
Max players The slot count is 0.
ts100
Group limit Teams hold no more than 100.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Mods and access

^o
Oxide The plugin framework is Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded