Rust Server TrendsSeismic network · station log
Recording Stations11,626 Players31,131 Active2,740 Wipes · 3 h70 48 h

Station XX-15948 · no signal

TraderEvents Test

Offline 52.14.104.140:28515 checked 26d ago

moddedoxide
Connect
Players now
0/ 4
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,948
top 70%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15948 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 4 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 152 on average
41/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
122/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
0/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
16/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
2/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
4/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on TraderEvents Test?

A procedural map runs on TraderEvents Test, generated by the game.

Which settings and rules apply on TraderEvents Test?

You will find no gather rate in the name of TraderEvents Test. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on TraderEvents Test?

A reading taken now finds TraderEvents Test offline; the most recent activity was 26 days 8 hours ago.

How does TraderEvents Test rank against other Rust servers?

Over the last seven days, TraderEvents Test recorded enough player hours to reach #15,948 worldwide, placing it in the top 70% of all ranked servers.

Server facts

How reliably does TraderEvents Test stay online?

As recorded now, TraderEvents Test is not reachable, the last contact having been 26 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is TraderEvents Test hosted?

No region is published by TraderEvents Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 52.14.104.140:28515 is the address it uses.

What build of Rust does TraderEvents Test use?

On Linux, TraderEvents Test runs Rust network protocol 2634 and build 166494. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

On what timetable does TraderEvents Test run its wipes?

Too few wipes of TraderEvents Test are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 27 days 10 hours.

Tags

What do the server tags on TraderEvents Test mean?

The game's server browser reads the tags TraderEvents Test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): Slots: 4; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166494 (Build): Game build: 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does TraderEvents Test appear?

The Rust Server Trends lists that take in TraderEvents Test are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

How do you connect to TraderEvents Test?

Enter client.connect 52.14.104.140:28515 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp4
Max players Slots: 4.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166494
Build Game build: 166494.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.