Offline 178.222.157.41:28025 checked 10d ago
DeepSea local validation
Connect
srv = rust.server("178.222.157.41:28027")
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 70% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 15:16 UTC10d ago | 0 | 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
- 178.222.157.41:28025
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 15:37 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 · 155 on average | 175/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 132/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 16/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 55/1000 |
Quick answers
From the figures on this page.
Player counts
How does DeepSea local validation compare in the rankings?
Rank #15,295 on seven-day player hours for DeepSea local validation, within the top 70% of all ranked servers.
How full does DeepSea local validation run?
Offline now for DeepSea local validation, with the last sample 10 days 14 hours ago.
Server facts
Which Rust version is DeepSea local validation on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by DeepSea local validation. Steam updates your game for you, but the protocol must match to join.
How reliable is DeepSea local validation, and is it online now?
DeepSea local validation is offline at this refresh; the last response came 10 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 17 October 2026.
In which location is DeepSea local validation hosted?
For DeepSea local validation, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.222.157.41:28025 is its address.
Map and rules
What rules and settings are recorded for DeepSea local validation?
No gather rate appears in the name: DeepSea local validation. No custom cap; the default of 8 players per group stands. 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. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has DeepSea local validation selected?
A procedural map runs on DeepSea local validation, generated by the game.
Wipes and dates
On what schedule does DeepSea local validation wipe?
The record for DeepSea local validation 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. A new world was started 10 days 20 hours ago, and that is the one in play.
On DeepSea local validation, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does DeepSea local validation appear among Rust Data lists and filters?
The Rust Data lists that DeepSea local validation fits are: 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 DeepSea local validation?
These tags are published by DeepSea local validation and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join DeepSea local validation?
Enter client.connect 178.222.157.41:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.