Live coverage · Rust server
Offline Event Testing is not on the server list right now. The figures below are from when it was last seen, 42d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
The record holds too few of Event Testing's wipes to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world dates from 43 days 18 hours.
On Rust Live Stats, Event Testing is listed under Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
gmrust (Game mode): Survival here follows standard Rust; mp0 (Max players): The slot count is 0; ts8 (Group limit): Team cap: 8, which is the game default; v2633 (Protocol): You need protocol 2633 on your game to get in; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Modded: plugins or changed settings alter the game: that is the tag list Event Testing publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Event Testing is not online at the moment, having last been seen 42 days 8 hours ago.
Player hours over seven days put Event Testing at #15,471, in the top 71% of all ranked servers.
Nothing in the name of Event Testing states a gather rate. No custom limit is set, so groups hold the default 8 players. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
Size 4,800, seed 1337: that is the procedural map the game generates for Event Testing. Size and seed repeat the same map, so RustMaps can show it from this page. Map name, as listed: Custom Map.
There is no region from Event Testing. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 82.215.64.19:28024.
Rust network protocol 2633 and build 163794 on Linux is what Event Testing runs. Steam updates it for you, but your game needs the same protocol to join.
Event Testing is currently offline, with its last appearance 42 days 8 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. The first sighting by Rust Live Stats was on 15 September 2026.
Enter client.connect 82.215.64.19:28024 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.