Offline 82.215.64.19:28015 checked 22d ago
OT Events
Connect
srv = rust.server("82.215.64.19:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 133/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 48/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 242/700 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does OT Events rank?
Over the last seven days OT Events sits at #15,983 on player hours, in the top 71% of ranked servers.
What population does OT Events carry?
The current row shows OT Events offline; the last response was 22 days 18 hours ago.
Server facts
What Rust version does OT Events run?
The build is Rust network protocol 2633 and build 165217 on Linux, run by OT Events. Steam updates your game for you, but the protocol must match to join.
Is OT Events up, and what does its uptime show?
OT Events is offline at this refresh; the last response came 22 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 16 September 2026.
In which location is OT Events hosted?
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:28015.
Map and rules
Which rules apply on OT Events, and what settings?
No gather rate appears in the name: OT Events. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on OT Events?
OT Events runs a procedural map of size 4,250 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipes and dates
On what schedule does OT Events wipe?
A rhythm cannot be read from the wipes of OT Events on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 54 days 10 hours ago, and that is the one in play.
Tags and filters
Where does OT Events appear among Rust Data lists and filters?
These Rust Data lists include OT Events: 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.
How should you read the server tags on OT Events?
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; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to OT Events?
In Rust, F1 opens the console: type client.connect 82.215.64.19:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. https://oilteam.gg/ is the website recorded for it.