Event Testing OT
Offline 37.148.220.87:28045 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
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
Player counts
How does Event Testing OT rank against other Rust servers?
Over the past week it ranks #15,498 for player hours, which puts Event Testing OT in the top – of all ranked servers.
How busy is Event Testing OT?
Event Testing OT is offline at this count; we last saw it 42 days 11 hours ago.
Lists and tags
What do the server tags on Event Testing OT mean?
What the game's server browser reads from Event Testing OT is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp0 (Max players): You can join up to 0 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2632 (Protocol): To join, your game must match protocol 2632; cs161125 (Build): The game build is 161125; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Event Testing OT?
Event Testing OT appears among the Rust Population lists that follow: 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 notes
What is the wipe schedule on Event Testing OT?
Too few wipes are on record for Event Testing OT to show its rhythm. 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 64 days 5 hours ago.
Settings
Which map does Event Testing OT run?
The map on Event Testing OT is procedural, made by the game.
What are the rules and settings on Event Testing OT?
Nothing in Event Testing OT's name says how gather works. The group limit is 8 players, which is the default. survival is what it runs, raid, build and gather: the standard game. Combat between players, raids included, is permitted. Modded is its browser category: plugins or settings change the game. You will find Oxide running as plugins. VAC, Valve's anti-cheat, runs here.
Server details
Which version of Rust does Event Testing OT run?
On Linux, Event Testing OT runs Rust network protocol 2632 and build 161125. Steam updates your game automatically, but you need the same protocol to join.
Is Event Testing OT online, and how reliable is it?
We last saw Event Testing OT 42 days 11 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. The first sighting by Rust Population was on 13 September 2026.
Where is Event Testing OT located?
A region is not published by Event Testing OT. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 37.148.220.87:28045.
Getting in
How do I join Event Testing OT?
To connect directly, open Rust's console with F1 and type client.connect 37.148.220.87:28045; or press Launch Rust on this page and Steam opens Rust and joins for you.