Offline 46.19.66.6:28015 checked 38d ago
Diamond Blue TEST
Connect
srv = rust.server("46.19.66.6: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, measured since 19 Sep. 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Saturday 31 October, 20:12 UTC, in 3d 15h. # Weekly: 7 days after its last 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
2500 · seed 87521200- map
- Procedural Map
- size
- 2500
- seed
- 87521200
Server
srv.info()- address
- 46.19.66.6:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 19 Sep 2026, 20:12 UTC
- hostname
- ^
- first seen
- 19 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 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 53/225 |
| 2 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 3 | [NA] Willjum's Solo Only | Thursday Wipes | NA · groups of 8+ · weekly · 26 on average | 10/100 |
| 4 | [EU] Willjum's Solo Only | Thursday Wipes | EU · groups of 8+ · weekly · 25 on average | 3/175 |
| 5 | QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 23 on average | 31/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Diamond Blue TEST rank?
Player hours over seven days put Diamond Blue TEST at #15,490, in the top 69% of the ranked set.
How many players does Diamond Blue TEST hold at once?
The current row shows Diamond Blue TEST offline; the last response was 38 days 7 hours ago.
About the server
Which Rust version is Diamond Blue TEST on?
Rust network protocol 2633 and build 164530 on Windows is what Diamond Blue TEST runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Diamond Blue TEST, and is it up?
Offline now for Diamond Blue TEST, last seen 38 days 7 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 19 September 2026.
In which location is Diamond Blue TEST hosted?
No region is published by Diamond Blue TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. 46.19.66.6:28015 is its address.
Settings and map
What rules and settings are recorded for Diamond Blue TEST?
The name Diamond Blue TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Diamond Blue TEST selected?
Size 2,500, seed 87521200: the procedural map on Diamond Blue TEST, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
On what schedule does Diamond Blue TEST wipe?
An estimate from weekly: 7 days after its last wipe gives Diamond Blue TEST's next wipe. On Saturday 31 October at 20:12 UTC the next wipe is due. This world was created 38 days 8 hours ago. The tags list wipes as weekly.
Tags and filters
Where does Diamond Blue TEST appear among Rust Data lists and filters?
These Rust Data lists include Diamond Blue TEST: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Which meanings do the tags on Diamond Blue TEST hold?
These tags are published by Diamond Blue TEST and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): The server runs build 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^w (Weekly): The interval is one week; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 into Diamond Blue TEST?
The manual route: launch Rust, F1, then client.connect 46.19.66.6:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.