Offline 98.117.202.167:28195 checked 12d ago
Saltwake private client test
Connect
srv = rust.server("98.117.202.167:28197")
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 98.117.202.167:28195
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 08:39 UTC
- hostname
- –
- first seen
- 17 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 | 152/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 79/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 16/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 83 on average | 256/700 |
Quick answers
From the figures on this page.
Population
What position does Saltwake private client test take in the server rankings?
Player hours over seven days put Saltwake private client test at #15,222, in the top 70% of the ranked set.
What population does Saltwake private client test carry?
The current row shows Saltwake private client test offline; the last response was 12 days 3 hours ago.
Server data
Which Rust version is Saltwake private client test on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Saltwake private client test. The protocol has to match before you can join, and Steam does the updating.
How reliable is Saltwake private client test, and is it up?
Saltwake private client test is offline at this refresh; the last response came 12 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 17 October 2026.
Where does Saltwake private client test sit?
No region is published by Saltwake private client test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 98.117.202.167:28195 is its address.
Rules, settings, map
Which rules apply on Saltwake private client test, and what settings?
The name Saltwake private client test carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Saltwake private client test selected?
Saltwake private client test runs a procedural map, which the game generates.
Wipe schedule
When does Saltwake private client test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Saltwake private client test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 12 days 4 hours ago.
Tags, lists
Which lists on Rust Data hold Saltwake private client test, and which filters?
These Rust Data lists include Saltwake private client test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on Saltwake private client test?
Read by the game's server browser, the tags Saltwake private client test publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into Saltwake private client test?
In Rust, F1 opens the console: type client.connect 98.117.202.167:28195. Launch Rust on this page does the same by opening the game through Steam and connecting.