Offline 52.14.104.140:28515 checked 26d ago
TraderEvents Test
Connect
srv = rust.server("52.14.104.140:28517")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 52.14.104.140:28515
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:49 UTC
- hostname
- –
- first seen
- 1 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 179/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 86/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 22/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 268/700 |
Quick answers
From the figures on this page.
Population
How does TraderEvents Test compare in the rankings?
Player hours over seven days put TraderEvents Test at #15,948, in the top 70% of the ranked set.
How many players does TraderEvents Test hold at once?
Offline now for TraderEvents Test, with the last sample 26 days 16 hours ago.
Server data
What is the Rust version on TraderEvents Test?
Rust network protocol 2634 and build 166494 on Linux is what TraderEvents Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is TraderEvents Test, and is it up?
TraderEvents Test is offline at this refresh; the last response came 26 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 1 October 2026.
Which location does TraderEvents Test run from?
There is no region published for TraderEvents Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 52.14.104.140:28515 is its address.
Settings and map
Which settings and rules does TraderEvents Test run?
The name TraderEvents Test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TraderEvents Test selected?
A procedural map runs on TraderEvents Test, generated by the game.
Wipes and dates
When does TraderEvents Test wipe, and on what schedule?
Too few wipes are on record for TraderEvents Test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 27 days 18 hours ago.
Tags, lists
Which Rust Data filters and lists contain TraderEvents Test?
These Rust Data lists include TraderEvents Test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TraderEvents Test?
These tags are published by TraderEvents Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): 4 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into TraderEvents Test?
The manual route: launch Rust, F1, then client.connect 52.14.104.140:28515. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.