Event Testing
Offline 82.215.64.19:28024 checked 42d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Quick answers
Population
How does Event Testing rank against other Rust servers?
The last seven days of player hours place Event Testing at #15,471, within the top 71% of all ranked servers.
How busy is Event Testing?
At this count Event Testing is offline, with its last sighting 42 days 8 hours ago.
Lists and tags
What do the server tags on Event Testing mean?
What the game's server browser reads from Event Testing is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): The server has 0 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2633 (Protocol): The protocol is 2633; a different version will not connect; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): This server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include Event Testing?
These Rust Population lists include Event Testing: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Wipe schedule
What is the wipe schedule on Event Testing?
Its rhythm cannot be told yet: too few of Event Testing's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 43 days 18 hours ago.
Map and rules
Which map does Event Testing run?
The map on Event Testing is procedural, made by the game at size 4,800 from seed 1337. The map follows from its size and seed, and RustMaps shows it from this page. The name on the map is Custom Map.
What are the rules and settings on Event Testing?
No gather rate appears in the name of Event Testing. No limit is set beyond the standard 8 players per group. You get survival here, raid, build and gather: the standard game. You can raid and fight other players here. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. VAC, Valve's anti-cheat, runs here.
About the server
Which version of Rust does Event Testing run?
Rust network protocol 2633 and build 163794 on Linux is what Event Testing uses. The protocol must match for you to join, and Steam updates it for you.
Is Event Testing online, and how reliable is it?
We last saw Event Testing 42 days 8 hours ago, and it is offline now. It was up 0% of the time over the last 7 full days, 0 out of 168 hours. On 15 September 2026, Rust Population saw it for the first time.
Where is Event Testing located?
A region is not published by Event Testing. The location a server claims is what Rust Population shows, not the place where the machine stands. You will find it at 82.215.64.19:28024.
Getting in
How do I join Event Testing?
Either enter client.connect 82.215.64.19:28024 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.