Station XX-13488 · no signal
Event Test Server
Offline 178.208.104.115:28035 checked 16d ago
- Players now
- 1/ 20
- 5% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,488
- top 61%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 20 slots
- Motion · 24 h
- M –not enough readings
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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.4 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 11 Oct, 21:03 UTC16d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 11 Oct, 11:56 UTC16d ago | M0.0■steady | 1 | – | 0.4 days | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Event Test Server?
A procedural map runs on Event Test Server, generated by the game.
Which settings and rules apply on Event Test Server?
You will find no gather rate in the name of Event Test Server. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on Event Test Server right now?
A reading taken now finds Event Test Server offline; the most recent activity was 16 days 13 hours ago.
How does Event Test Server rank against other Rust servers?
Over the last seven days, Event Test Server recorded enough player hours to reach #13,488 worldwide, placing it in the top 61% of all ranked servers.
Server facts
How reliably does Event Test Server stay online?
Event Test Server is down at the moment; the last recorded contact was 16 days 13 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 11 October 2026.
Which region does Event Test Server run from?
A region is not published by Event Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 178.208.104.115:28035 is the address it uses.
Which Rust version is Event Test Server running?
Rust network protocol 2634 and build 167398 on Windows is what Event Test Server runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Event Test Server?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Event Test Server run its wipes?
On record so far are too few of Event Test Server's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 16 days 14 hours.
Tags
What do the server tags on Event Test Server mean?
These are the tags Event Test Server publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): Slots: 20; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): The game build is 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Event Test Server appear?
The Rust Server Trends lists that take in Event Test Server are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
What steps get you onto Event Test Server?
Enter client.connect 178.208.104.115:28035 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.