Offline 178.172.240.122:28015 checked 11d ago
TEST
Connect
srv = rust.server("178.172.240.122:28017")
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 53% 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, 4 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 13 Oct, 10:08 UTC15d ago | 2 | NaN | running | 1 |
| 1 | Fri 9 Oct, 19:38 UTC19d ago | 1 | held half | 3.6 days | 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.172.240.122:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 13:59 UTC
- hostname
- –
- first seen
- 2 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 · 155 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 11/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TEST rank?
Rank #11,497 on seven-day player hours for TEST, within the top 53% of all ranked servers.
What population does TEST carry?
TEST returns no live count at this refresh, having last been seen 11 days 6 hours ago.
About the server
What Rust version does TEST run?
Version Rust network protocol 2634 and build 166652 on Windows is reported by TEST. The protocol has to match before you can join, and Steam does the updating.
Is TEST up, and what does its uptime show?
The latest sample has TEST offline, with a last sighting 11 days 6 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 2 October 2026.
Where does TEST sit?
No region is published by TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 178.172.240.122:28015.
Map and rules
What rules and settings are recorded for TEST?
You will not find a gather rate in the string TEST. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has TEST loaded?
A procedural map runs on TEST, generated by the game.
Wipe schedule
When does TEST wipe, and on what schedule?
Too few wipes are on record for TEST to reveal its 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 15 days 12 hours ago.
On TEST, what happens on wipe day?
The average peak over recent wipes is 2 players. 4 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Where does TEST appear among Rust Data lists and filters?
These Rust Data lists include TEST: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TEST?
The game's server browser reads these tags from TEST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join TEST?
The manual route: launch Rust, F1, then client.connect 178.172.240.122:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.