Offline 192.154.104.162:28015 checked 9d ago
PantiNet relay test
Connect
srv = rust.server("192.154.104.162: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 66% 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 | Mon 19 Oct, 18:03 UTC9d 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
- 192.154.104.162:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 18:49 UTC
- hostname
- –
- first seen
- 19 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 · 157 on average | 105/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 116 on average | 119/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 90/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 25/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
Quick answers
From the figures on this page.
Player counts
How does PantiNet relay test compare in the rankings?
Player hours over seven days put PantiNet relay test at #14,584, in the top 66% of the ranked set.
What population does PantiNet relay test carry?
The current row shows PantiNet relay test offline; the last response was 9 days 2 hours ago.
Server data
Which Rust version is PantiNet relay test on?
Rust network protocol 2634 and build 167781 on Windows is what PantiNet relay test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is PantiNet relay test, and is it online now?
Offline now for PantiNet relay test, last seen 9 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 19 October 2026.
In which location is PantiNet relay test hosted?
No region is published by PantiNet relay 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 192.154.104.162:28015.
Settings and map
Which rules apply on PantiNet relay test, and what settings?
No gather rate appears in the name: PantiNet relay test. The group limit sits at the default of 8 players. 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. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has PantiNet relay test selected?
The game generates its map: procedural, on PantiNet relay test.
Wipe data
On what schedule does PantiNet relay test wipe?
A rhythm cannot be read from the wipes of PantiNet relay test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 9 days 2 hours ago, and that is the one in play.
On PantiNet relay test, what happens on wipe day?
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 PantiNet relay test appear among Rust Data lists and filters?
The Rust Data lists that PantiNet relay test fits are: 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on PantiNet relay test hold?
The game's server browser reads these tags from PantiNet relay test: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join PantiNet relay test?
In Rust, F1 opens the console: type client.connect 192.154.104.162:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.