RS-15948Modded server
TraderEvents Test
Offline 52.14.104.140:28515 checked 12d 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
Top 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
| 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.
Quick answers
From the figures on this page.
Player activity
How many players are usually on TraderEvents Test?
TraderEvents Test is offline at this moment; the last signal was 12 days 10 hours ago.
Where does TraderEvents Test sit in the rankings?
On player hours across seven days, TraderEvents Test is #15,948, inside the top 70% of all ranked servers.
Tags and filters
Where does TraderEvents Test show up in Top Rust Servers lists and filters?
These Top Rust Servers lists include TraderEvents Test: Top modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on TraderEvents Test?
gmrust (Game mode): Standard survival, as in Rust; mp4 (Max players): There are 4 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs166494 (Build): The game build is 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is assigned; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): It appears in Modded, as plugins or settings modify the game are the tags TraderEvents Test publishes, and the game's server browser reads them. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Rules, settings, and map
Which map is running on TraderEvents Test?
A procedural map, created by the game, is in use on TraderEvents Test.
What settings and rules does TraderEvents Test use?
You will not find a gather rate in the name TraderEvents Test. Up to 8 players per group, as the game defaults. It runs survival, standard survival: gathering, building and raiding. Player versus player combat and raiding are enabled. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are loaded. VAC, Valve's anti-cheat, is enabled.
About the server
What version is TraderEvents Test running?
On Linux, TraderEvents Test operates Rust network protocol 2634 and build 166494. Your game needs the same protocol to connect; Steam takes care of updating it.
Where can TraderEvents Test be found?
A region is not published by TraderEvents Test. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 52.14.104.140:28515.
How reliable is TraderEvents Test?
The server TraderEvents Test is down at the moment, with its last appearance 12 days 10 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. The first time Top Rust Servers saw it was on 1 October 2026.
Wipe schedule
How often does TraderEvents Test wipe?
Not enough wipe data exists yet to identify the rhythm of TraderEvents Test. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 13 days 12 hours ago.
Joining the server
What is the process to join TraderEvents Test?
To connect, start Rust, hit F1, and enter client.connect 52.14.104.140:28515. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.