Online 185.250.36.125:28015 checked 8m ago
chilling_wave
Connect
srv = rust.server("185.250.36.125: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 17 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 bestTop 69% 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
2000 · seed 78955152
- map
- Procedural Map
- size
- 2000
- seed
- 78955152
Server
srv.info()- address
- 185.250.36.125:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 02:06 UTC
- hostname
- –
- first seen
- 13 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 | 127/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 195/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 74/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 222/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population
What position does chilling_wave take in the server rankings?
Over the last seven days chilling_wave sits at #15,310 on player hours, in the top 69% of ranked servers.
What population does chilling_wave carry?
chilling_wave reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.
Server facts
How smoothly does chilling_wave run?
Averaged over 48 hours: 51 server fps, never under 13. Entity numbers reached 26,590, and that includes buildings, deployables and the rest. Memory peaked at 1,050 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does chilling_wave run?
The build is Rust network protocol 2633 and build 162929 on Linux, run by chilling_wave. Steam updates your game for you, but the protocol must match to join.
Is chilling_wave up, and what does its uptime show?
The current sample puts chilling_wave online. A restart about 5 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does chilling_wave sit?
No region is published by chilling_wave. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.250.36.125:28015.
Settings and map
What rules and settings are recorded for chilling_wave?
You will not find a gather rate in the string chilling_wave. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. 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 chilling_wave loaded?
Size 2,000, seed 78955152: the procedural map on chilling_wave, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
On what schedule does chilling_wave wipe?
Too few wipes are on record for chilling_wave to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 55 days 16 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain chilling_wave?
These Rust Data lists include chilling_wave: 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.
How should you read the server tags on chilling_wave?
The game's server browser reads these tags from chilling_wave: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs162929 (Build): Recorded game build: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
How can I connect to chilling_wave?
Enter client.connect 185.250.36.125:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.