OT Events

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 82.215.64.19:28021

Abstract

We describe the public Rust server OT Events, reached at 82.215.64.19:28021. At the last check it held 0 of an unpublished number of places, against a seven-day mean of 3 and a peak of 82¹. It ranks #1,773 of all servers, the top 8%. It last wiped 1d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/?	no limit published
In the queue	0	no queue
Seven-day mean	3	peak 82, 48 h peak 1
Rank²	#1,773	top 8%
Last wipe	1d ago	no schedule published
Next wipe³	–	no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeakWipe

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

Server fpsWipe

Figure 2: Server performance. 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.

4Rank

The server stands in the top 8% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	6.3 days	between real wipes
On rhythm	0%	of its recent wipes
Wipe-day peak	55	players, last three wipes
Crowd held	0%	else halves by day 1

Sat 24 OctFri 23 OctWed 14 Oct

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 82, 4 hours in, with 1 in the queue.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Tue 27 Oct, 20:151d ago	–	–	running	1
Sat 24 Oct, 12:435d ago	82+1	halved by day 1	3.3 d	0
Fri 23 Oct, 19:595d ago	82+1	–	0.7 d	0
Wed 14 Oct, 14:0414d ago	0	–	9.2 d	0
Thu 24 Sep, 03:1435d ago	1	halved by day 1	20.5 d	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of OT Events — Figure 5: The map: Custom Map, size 5000, seed 1337.

Table 4: The server's published settings.

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
Map	Custom Map
Size	5000
Seed	1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 149 on average	170/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	131/100
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average	75/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	16/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	23/1000
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 83 on average	252/700

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of OT Events smooth?

Its average server fps over the last 48 hours was 40, with a minimum of 40. Buildings, deployables and all other world objects counted together reached a maximum of 48,489 entities. Its highest memory usage was 3,904 MB. Players experience lag when fps is low and the entity count is rising.

A.2In which location is OT Events based?

A region is not published by OT Events. Rust Statistics does not look up the machine's location; it shows where the server says it is. 82.215.64.19:28021 is its address.

A.3What is the online status and reliability of OT Events?

At the present moment, OT Events is online. It last restarted around 37 hours ago, according to its reported uptime. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What is the Rust version for OT Events?

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

Wipe schedule

A.5What schedule does OT Events follow for wipes?

With irregular wipe times, OT Events offers no next wipe to predict. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 39 hours.

A.6What characterises wipe day on OT Events?

Recent wipes saw an average peak of 55 players. A peak 4 hours after the latest wipe was accompanied by 1 players waiting in the queue. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. Otherwise, a fall below half took place by day 1.

Population

A.7What is the rank of OT Events among Rust servers?

Ranked by player hours across seven days, OT Events holds #1,773, in the top 8% of all ranked servers.

A.8How would you characterise the player activity on OT Events?

OT Events is currently host to 0 players. Averaged over the last seven days: 3 players; the same period peaks at 82. Of the last 48 hours, the peak hour falls at 19:00 UTC, with an average of 1 players.

Tags, lists

A.9How should the tags on OT Events be interpreted?

Tags from OT Events, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp0 (Max players): 0 slots are available; ts100 (Group limit): 100 is the maximum team size; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can OT Events be found among the Rust Statistics lists and filters?

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

Settings and map

A.11Under what rules and settings does OT Events operate?

No gather rate appears in the name of OT Events. A group holds at most 100 players. The mode is survival, which means gathering, building and raiding, as the game is usually played. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on OT Events?

Generated by the game from seed 1337, the procedural map on OT Events measures 5,000. Because size and seed determine the map, RustMaps can show it, linked from this page. The map is named Custom Map.

How to join

A.13What steps are required to join OT Events?

Press F1 inside Rust to open the console and enter client.connect 82.215.64.19:28021. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp0,ptrak,$r?,v2635,gmrust,cs168909,ts100,^o^z.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp0`	Max players. 0 slots are available.
`ts100`	Group limit. 100 is the maximum team size.
`v2635`	Protocol. The game protocol is 2635; your client must match it to join.
`cs168909`	Build. Build 168909 is the one running.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Oxide (uMod), a plugin framework, runs on this server.
`^z`	Modded. The game is altered by plugins or settings, so it is listed as 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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.