Online 82.215.64.19:28018 checked 6m ago
OT Events
Connect
srv = rust.server("82.215.64.19:28020")
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 23 Oct. 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 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 72, 22 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 20:44 UTC6d ago | 72 | NaN | running | 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())
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 · 151 on average | 35/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 · 123 on average | 38/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 14/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 35/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 47/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does OT Events rank?
Player hours over seven days put OT Events at #4,421, in the top 20% 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 0 players and peaked at 72.
About the server
What does performance look like on OT Events?
Averaged over 48 hours: 40 server fps, never under 40. Buildings, deployables and all else in the world took the count as high as 59 entities. The memory field tops out at 2,318 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does OT Events run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by OT Events. Steam updates your game for you, but the protocol must match to join.
How reliable is OT Events, and is it online now?
The current sample puts OT Events online. Count back 5 days 14 hours from its reported uptime to get the last restart. 147 of 168 hours up over the last 7 full days, or 88%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does OT Events run from?
For OT Events, no region is published. 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:28018.
Map and rules
What rules and settings are recorded for OT Events?
The name OT Events carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: 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. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has OT Events selected?
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?
A rhythm cannot be read from the wipes of OT Events on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 8 hours ago.
What is wipe day on OT Events like?
The average peak over recent wipes is 72 players. The crowd on the latest wipe topped out 22 hours after it began.
Tags, lists
Which Rust Data filters and lists contain OT Events?
These Rust Data lists include OT Events: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on OT Events hold?
The game's server browser reads these tags from OT Events: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): 0 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join OT Events?
Enter client.connect 82.215.64.19:28018 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.