TraderEvents Test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 26d ago · 52.14.104.140:28515

Abstract

We describe the public Rust server TraderEvents Test, reached at 52.14.104.140:28515. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,948 of all servers, the top 70%. It last wiped 27d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/4	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,948	top 70%
Last wipe	27d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: 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.

4Rank

The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

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
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and upcoming Rust wipes [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 149 on average	169/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	128/100
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average	81/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	23/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	25/1000
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 84 on average	265/700

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of TraderEvents Test?

No region is published by TraderEvents Test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 52.14.104.140:28515.

A.2How reliable is TraderEvents Test, and is it currently online?

At the present moment, TraderEvents Test is offline; it was last seen 26 days 16 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 1 October 2026.

A.3What is the Rust version for TraderEvents Test?

Rust network protocol 2634 and build 166494 is the version that TraderEvents Test runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4When are wipes carried out on TraderEvents Test?

The record of TraderEvents Test's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 27 days 18 hours ago.

Population

A.5What position does TraderEvents Test occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts TraderEvents Test at #15,948, within the top 70% of ranked servers.

A.6How would you characterise the player activity on TraderEvents Test?

The last recorded sighting of TraderEvents Test was 26 days 16 hours ago; it is offline now.

Tags and filters

A.7How should the tags on TraderEvents Test be interpreted?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp4 (Max players): It offers 4 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166494 (Build): Build 166494 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which TraderEvents Test publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can TraderEvents Test be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that TraderEvents Test fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.9Which settings and rules are in force on TraderEvents Test?

No gather rate appears in the name of TraderEvents Test. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gather, build and raid: the standard game. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.10What is the map for TraderEvents Test?

The game generates the map on TraderEvents Test; that format is procedural.

Connection

A.11What steps are required to join TraderEvents Test?

Press F1 inside Rust to open the console and enter client.connect 52.14.104.140:28515. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp4,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp4`	Max players. It offers 4 slots.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs166494`	Build. Build 166494 is the one running.
`ptrak`	Networking. RakNet is the network layer here, as it is by default in the game.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Plugins are handled by Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.