Offline 188.163.123.246:28015 checked 5h ago
Drizzle Test
Connect
srv = rust.server("188.163.123.246: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 62% 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 | Thu 29 Oct, 22:55 UTC6h ago | NaN | NaN | running | 0 |
| 1 | Sun 4 Oct, 12:37 UTC25d ago | 1 | held half | 25.4 days | 1 |
# 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
- 188.163.123.246:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Oct 2026, 22:55 UTC
- hostname
- –
- first seen
- 18 Sep 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 · 151 on average | 32/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 0/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 9/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 30/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 50/200 |
Quick answers
From the figures on this page.
Population data
What position does Drizzle Test take in the server rankings?
Over the last seven days Drizzle Test sits at #13,823 on player hours, in the top 62% of ranked servers.
How full does Drizzle Test run?
The current row shows Drizzle Test offline; the last response was 5 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 1 players.
Server data
Which Rust version is Drizzle Test on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Drizzle Test. Joining needs the same protocol on your game; Steam handles the update.
Is Drizzle Test up, and what does its uptime show?
Drizzle Test is offline at this refresh; the last response came 5 hours ago. Uptime of 2% across the last 7 full days: 4 hours of 168. The first row Rust Data holds for it is dated 18 September 2026.
Which location does Drizzle Test run from?
No region is published by Drizzle Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 188.163.123.246:28015 is its address.
Rules, settings, map
Which settings and rules does Drizzle Test run?
You will not find a gather rate in the string Drizzle Test. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Drizzle Test selected?
Drizzle Test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Drizzle Test wipe?
A rhythm cannot be read from the wipes of Drizzle 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. The world it runs now was generated 6 hours ago.
What is wipe day on Drizzle Test like?
Recent wipes averaged 1 players at their peak. 0 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.
Tags, lists
Which lists on Rust Data hold Drizzle Test, and which filters?
These Rust Data lists include Drizzle Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the server tags on Drizzle Test?
The game's server browser reads these tags from Drizzle Test: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^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.
How to join
What is the way into Drizzle Test?
The manual route: launch Rust, F1, then client.connect 188.163.123.246:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.