Offline 149.50.40.198:28035 checked 26d ago
Event Test Server
Connect
srv = rust.server("149.50.40.198: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 best
Top 69% 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 | Thu 1 Oct, 15:26 UTC26d ago | 1 | NaN | running | 1 |
# 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
- 149.50.40.198:28035
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 15:26 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 · 159 on average | 45/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 52/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 27/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 8/1000 |
Quick answers
From the figures on this page.
Population data
How does Event Test Server compare in the rankings?
Rank #16,330 on seven-day player hours for Event Test Server, within the top 69% of all ranked servers.
What population does Event Test Server carry?
The current row shows Event Test Server offline; the last response was 26 days 11 hours ago.
Server data
Which Rust version is Event Test Server on?
Rust network protocol 2633 and build 165217 on Windows is what Event Test Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Event Test Server, and is it up?
Offline now for Event Test Server, last seen 26 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 1 October 2026.
Where does Event Test Server sit?
There is no region published for Event Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 149.50.40.198:28035.
Rules, settings, map
Which settings and rules does Event Test Server run?
You will not find a gather rate in the string Event Test Server. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
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. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 26 days 13 hours ago.
What is wipe day on Event Test Server like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does Event Test Server appear among Rust Data lists and filters?
These Rust Data lists include Event Test Server: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Event Test Server hold?
The game's server browser reads these tags from Event Test Server: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Event Test Server?
In Rust, F1 opens the console: type client.connect 149.50.40.198:28035. Launch Rust on this page does the same by opening the game through Steam and connecting.