Offline 5.206.104.226:28015 checked 27d ago
Happy Test
Connect
srv = rust.server("5.206.104.226:28016")
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, measured since 26 Sep. 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 60% 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 2, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 17:50 UTC32d ago | 2 | 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
3000 · seed 543625
- map
- Procedural Map
- size
- 3000
- seed
- 543625
Server
srv.info()- address
- 5.206.104.226:28015
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 18:58 UTC
- hostname
- –
- first seen
- 26 Sep 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 · 150 on average | 74/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 105/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 36/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Happy Test rank?
Player hours over seven days put Happy Test at #14,107, in the top 60% of the ranked set.
What population does Happy Test carry?
Happy Test returns no live count at this refresh, having last been seen 27 days 16 hours ago.
About the server
What Rust version does Happy Test run?
Rust network protocol 2633 and build 165217 on Windows is what Happy Test runs. Steam updates your game for you, but the protocol must match to join.
Is Happy Test up, and what does its uptime show?
Offline now for Happy Test, last seen 27 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 26 September 2026.
Which location does Happy Test run from?
No region is published by Happy Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 5.206.104.226:28015 is its address.
Settings and map
What rules and settings are recorded for Happy Test?
The name Happy Test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Happy Test loaded?
Happy Test runs a procedural map of size 3,000 with seed 543625, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does Happy Test wipe, and on what schedule?
The record for Happy Test holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 32 days 12 hours ago.
On Happy Test, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Where does Happy Test appear among Rust Data lists and filters?
The Rust Data lists that Happy Test fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Happy Test hold?
Read by the game's server browser, the tags Happy Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): Slot count: 30; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^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.
Join steps
How can I connect to Happy Test?
In Rust, F1 opens the console: type client.connect 5.206.104.226:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.