Event Testing OT
Offline 37.148.220.87:28045 checked 41d ago
Server instruments
no direct query in 48 hoursPlayers now
no slots published 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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- 160/500
- 120/100
- 186/225
- 109/700
- 7/200
- 44/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Event Testing OT follow?
To tell the rhythm of Event Testing OT, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 63 days 15 hours ago.
Tags
How should you read the tags on Event Testing OT?
These are the tags Event Testing OT publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): Slots: 0; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Match the game version: protocol 2632 is required; cs161125 (Build): Build 161125; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Event Testing OT?
Rust Metrics lists featuring Event Testing OT: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does Event Testing OT hold among Rust servers?
Ranking for Event Testing OT: #15,498 on seven-day player hours, top – of all ranked servers.
What is the population on Event Testing OT?
Event Testing OT is not responding; status offline, last seen 41 days 21 hours ago.
Server details
What location is Event Testing OT hosted in?
No region tag on Event Testing OT. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 37.148.220.87:28045.
What Rust version is Event Testing OT on?
Rust network protocol 2632 and build 161125 on Linux is the build Event Testing OT runs. Matching protocol is required to join. Let Steam update your game.
Is Event Testing OT up, and how often does it stay up?
Reading: offline. Event Testing OT last answered 41 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Map and rules
What settings and rules apply on Event Testing OT?
Reading the name gives no gather rate for Event Testing OT. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is Event Testing OT on?
Procedural map on Event Testing OT, made by the game's generator.
How to join
How do you connect to Event Testing OT?
Check: join. Open Rust, press F1, then enter client.connect 37.148.220.87:28045. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.