Offline 178.208.110.214:28035 checked 19d ago
Event Test Server
Connect
srv = rust.server("178.208.110.214:28037")
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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 18:37 UTC19d ago | 1 | NaN | running | 0 |
# 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
- 178.208.110.214:28035
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 22:49 UTC
- hostname
- –
- first seen
- 10 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 | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 182/215 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Event Test Server rank?
Player hours over seven days put Event Test Server at #13,628, in the top 62% of the ranked set.
How many players does Event Test Server hold at once?
Event Test Server returns no live count at this refresh, having last been seen 19 days ago.
About the server
Which Rust version is Event Test Server on?
Rust network protocol 2634 and build 167398 on Windows is what Event Test Server runs. Steam updates your game for you, but the protocol must match to join.
Is Event Test Server up, and what does its uptime show?
Offline now for Event Test Server, last seen 19 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 10 October 2026.
In which location is Event Test Server hosted?
No region is published by Event Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.208.110.214:28035 is its address.
Settings and map
Which rules apply on Event Test Server, and what settings?
You will not find a gather rate in the string Event Test Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Event Test Server?
Event Test Server runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Event Test Server wipe?
The record for Event Test Server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 19 days 1 hours ago.
What is wipe day on Event Test Server like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does Event Test Server appear among Rust Data lists and filters?
These Rust Data lists include Event Test Server: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Event Test Server?
Read by the game's server browser, the tags Event Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join Event Test Server?
Enter client.connect 178.208.110.214:28035 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.