chilling_wave
Online 185.250.36.125:28015 checked 13m ago
Server instruments
last reading Fri 03:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 24 · below 20 is lag, below 10 is badEntities
48 h range 21,782–26,806 · memory 838 MBUptime
4 h 1 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 29/500
- 123/100
- 55/225
- 10/700
- 29/700
- 53/200
Quick answers
from the figures on this pageWipe timing
How often does chilling_wave wipe, and when?
The rhythm of chilling_wave's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 56 days 2 hours ago.
Tag meanings
Which tags does chilling_wave carry, and what do they mean?
These are the tags chilling_wave publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Game build reading: 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does chilling_wave appear in Rust Metrics lists and filters?
Rust Metrics lists featuring chilling_wave: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does chilling_wave hold among Rust servers?
Ranking for chilling_wave: #15,270 on seven-day player hours, top 69% of all ranked servers.
What player count does chilling_wave carry?
Current headcount on chilling_wave: 0 players, 50 slots available. Seven-day reading: 0 players on average.
Operator and location
Where does chilling_wave sit?
No region comes from chilling_wave. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.250.36.125:28015.
What Rust version is chilling_wave on?
Version check: Rust network protocol 2633 and build 162929 on Linux, run by chilling_wave. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on chilling_wave within range?
Over the last 48 hours the average was 49 server fps; the floor was 24. Check: entities. The peak was 26,806, counting buildings, deployables and the rest of the world. Memory peak: 1,050 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on chilling_wave, and is it online?
Reading: online. chilling_wave answers right now. Reading: uptime. About 4 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
How is chilling_wave configured, and what rules are in force?
Check: gather rate. The name chilling_wave does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
What map is chilling_wave on?
From seed 78955152, the game generates the procedural map on chilling_wave. Its size is 2,000. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How do you connect to chilling_wave?
Press F1 in Rust and enter client.connect 185.250.36.125:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.