Event Testing OT
Offline 37.148.220.87:28045 checked 31d ago
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
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 12/ 100
- 112/ 400
- 69/ 225
- 124/ 100
- 112/ 1000
- 6/ 700
Quick answers
Tags and filters
Where does Event Testing OT appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Event Testing OT: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on Event Testing OT?
gmrust (Game mode): Survival, as standard Rust does it; mp0 (Max players): It holds 0 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2632 (Protocol): To join, your game has to be on protocol 2632; cs161125 (Build): The build number is 161125; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Event Testing OT puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What location is Event Testing OT in?
No region comes from Event Testing OT. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 37.148.220.87:28045.
Is Event Testing OT up, and how often does it stay online?
Right now Event Testing OT is offline, having last been seen 31 days 16 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 13 September 2026.
What Rust version is Event Testing OT on?
The version on Event Testing OT is Rust network protocol 2632 and build 161125, on Linux. The protocol must match to join; Steam will update your game.
Wipe info
How often does Event Testing OT wipe?
The wipes recorded for Event Testing OT are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 53 days 10 hours ago.
Settings and map
What settings are in place on Event Testing OT?
No gather rate appears in the name of Event Testing OT. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
What's the map on Event Testing OT?
Event Testing OT uses a game-generated procedural map.
Population
How many players are on Event Testing OT?
The last sighting of Event Testing OT was 31 days 16 hours ago; it is offline right now.
What position does Event Testing OT hold in the server rankings?
For player hours in the last seven days, Event Testing OT ranks #15,498, within the top – of ranked servers.
How to join
What's the process to join Event Testing OT?
Open Rust and press F1, then type client.connect 37.148.220.87:28045. Alternatively, click Launch Rust on this page to join via Steam.