Rust Data

rustdata.spaceservers82.215.64.19:28023.ipynb

Run all rust-data · live

‹ All servers

Online 82.215.64.19:28021 checked 9m ago

OT Events

moddedoxide

Connect

srv = rust.server("82.215.64.19:28023")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 3 # peak 82
rank #1,771 # top 8%
last wipe 1d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75114:0023:0008:0017:0003:0012:00Wiped Tue 27 Oct, 20:15 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
01020304014:0023:0008:0017:0003:0012: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 20:15 UTC1d ago NaN NaN running 1
1 Sat 24 Oct, 12:43 UTC5d ago 82+1 queue halved by day 1 3.3 days 0
2 Fri 23 Oct, 19:59 UTC5d ago 82+1 queue NaN 0.7 days 0
3 Wed 14 Oct, 14:04 UTC14d ago 0 NaN 9.2 days 0
4 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.

display(srv.map, srv.info())

Map

5000 · seed 1337
Map of OT Events
map
Custom Map
size
5000
seed
1337

Server

srv.info()
address
82.215.64.19:28021
region
–
max players
–
group limit
100 max
wipe schedule
–
last wipe
27 Oct 2026, 21:02 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 149 on average184/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average121/100
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average86/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average28/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average28/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average265/700

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does OT Events rank?

Player hours over seven days put OT Events at #1,771, in the top 8% of the ranked set.

How full does OT Events run?

0 is the count in the players field for OT Events at this refresh. Over the last seven days it averaged 3 players and peaked at 82. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 1 players.

About the server

What does performance look like on OT Events?

Server fps over the last 48 hours averages 40; the floor is 40. Entity numbers reached 48,489, and that includes buildings, deployables and the rest. The memory field tops out at 3,904 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on OT Events?

The build is Rust network protocol 2635 and build 168909 on Linux, run by OT Events. Joining needs the same protocol on your game; Steam handles the update.

Is OT Events up, and what does its uptime show?

The current sample puts OT Events online. The uptime it reports puts the last restart about 38 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

Which location does OT Events run from?

There is no region published for OT Events. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 82.215.64.19:28021.

Rules, settings, map

What rules and settings are recorded for OT Events?

You will not find a gather rate in the string OT Events. Group size tops out at 100 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

What is the map on OT Events?

OT Events runs a procedural map of size 5,000 with seed 1337, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.

Wipe schedule

When does OT Events wipe, and on what schedule?

OT Events wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 40 hours ago.

On OT Events, what happens on wipe day?

Recent wipes averaged 55 players at their peak. A peak 4 hours into the latest wipe, plus 1 waiting in the queue. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Where does OT Events appear among Rust Data lists and filters?

On Rust Data, OT Events appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on OT Events hold?

Read by the game's server browser, the tags OT Events publishes are: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): Slot count: 0; ts100 (Group limit): The team cap is 100; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into OT Events?

In Rust, F1 opens the console: type client.connect 82.215.64.19:28021. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp0
Max players Slot count: 0.
ts100
Group limit The team cap is 100.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under 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.

Rust Data 73,470 players 11,849 servers online