Offline 82.215.64.19:28024 checked 42d ago
Event Testing
Connect
srv = rust.server("82.215.64.19:28026")
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. 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 bestTop 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())Map
4800 · seed 1337
- map
- Custom Map
- size
- 4800
- seed
- 1337
Server
srv.info()- address
- 82.215.64.19:28024
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Sep 2026, 20:07 UTC
- hostname
- –
- first seen
- 15 Sep 2026
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 | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 169/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 100/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 244/700 |
Quick answers
From the figures on this page.
Population data
How does Event Testing compare in the rankings?
Over the last seven days Event Testing sits at #15,471 on player hours, in the top 71% of ranked servers.
How many players does Event Testing hold at once?
Event Testing returns no live count at this refresh, having last been seen 42 days 8 hours ago.
Server facts
Which Rust version is Event Testing on?
Version Rust network protocol 2633 and build 163794 on Linux is reported by Event Testing. The protocol has to match before you can join, and Steam does the updating.
How reliable is Event Testing, and is it up?
Offline now for Event Testing, last seen 42 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 15 September 2026.
In which location is Event Testing hosted?
There is no region published for Event Testing. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 82.215.64.19:28024.
Rules, settings, map
Which settings and rules does Event Testing run?
You will not find a gather rate in the string Event Testing. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Event Testing?
Event Testing runs a procedural map of size 4,800 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 Event Testing wipe, and on what schedule?
A rhythm cannot be read from the wipes of Event Testing 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 43 days 18 hours ago, and that is the one in play.
Lists and tags
Where does Event Testing appear among Rust Data lists and filters?
These Rust Data lists include Event Testing: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Event Testing hold?
Read by the game's server browser, the tags Event Testing publishes are: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $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. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join Event Testing?
Enter client.connect 82.215.64.19:28024 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.