Offline 178.55.161.163:28015 checked 9d ago
DeptyZ Testing
Connect
srv = rust.server("178.55.161.163: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 bestTop 55% 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 3, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 19 Oct, 20:51 UTC9d ago | 3 | 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.55.161.163:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 22:05 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 · 156 on average | 4/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 · 117 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 38/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does DeptyZ Testing rank?
Over the last seven days DeptyZ Testing sits at #12,132 on player hours, in the top 55% of ranked servers.
What population does DeptyZ Testing carry?
DeptyZ Testing returns no live count at this refresh, having last been seen 9 days 1 hours ago.
About the server
Which Rust version is DeptyZ Testing on?
Rust network protocol 2634 and build 167781 on Windows is what DeptyZ Testing runs. Joining needs the same protocol on your game; Steam handles the update.
Is DeptyZ Testing up, and what does its uptime show?
Offline now for DeptyZ Testing, last seen 9 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 19 October 2026.
In which location is DeptyZ Testing hosted?
For DeptyZ Testing, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.55.161.163:28015 is its address.
Map and rules
Which rules apply on DeptyZ Testing, and what settings?
You will not find a gather rate in the string DeptyZ Testing. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. 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.
What is the map on DeptyZ Testing?
A procedural map runs on DeptyZ Testing, generated by the game.
Wipe schedule
On what schedule does DeptyZ Testing wipe?
A rhythm cannot be read from the wipes of DeptyZ Testing on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 9 days 2 hours ago.
On DeptyZ Testing, what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which lists on Rust Data hold DeptyZ Testing, and which filters?
The Rust Data lists that DeptyZ Testing fits are: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on DeptyZ Testing?
These tags are published by DeptyZ Testing and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; 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): The Modded section lists it, because plugins or settings change the game. 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 DeptyZ Testing?
The manual route: launch Rust, F1, then client.connect 178.55.161.163:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.