TraderEvents Test
Offline 52.14.104.140:28515 checked 15d 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 bestTop 70% 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
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
- 17/ 100
- 300/ 400
- 174/ 225
- 128/ 100
- 345/ 1000
- 26/ 700
Quick answers
Tags and listings
Where does TraderEvents Test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TraderEvents Test are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TraderEvents Test?
The server browser shows these tags for TraderEvents Test: gmrust (Game mode): Survival, as standard Rust does it; mp4 (Max players): It holds 4 players; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166494 (Build): The build number is 166494; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of TraderEvents Test?
TraderEvents Test does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 52.14.104.140:28515.
Is TraderEvents Test up, and how often does it stay online?
Right now TraderEvents Test is offline, having last been seen 15 days 13 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 1 October 2026.
What is the Rust version for TraderEvents Test?
Rust network protocol 2634 and build 166494 is what TraderEvents Test runs, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
How often does TraderEvents Test wipe?
TraderEvents Test's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 16 days 15 hours ago.
Rules and settings
What settings and rules have been applied to TraderEvents Test?
Its name does not state a gather rate for TraderEvents Test. 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. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. The server runs Valve's anti-cheat, VAC.
Which map is active on TraderEvents Test?
TraderEvents Test uses a game-generated procedural map.
Population
Is TraderEvents Test busy?
TraderEvents Test was last seen 15 days 13 hours ago and is offline as you read this.
What position does TraderEvents Test hold in the server rankings?
Over the last seven days, TraderEvents Test is #15,948 by player hours, among the top 70% of all ranked servers.
Getting in
What's the way to join TraderEvents Test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 52.14.104.140:28515.