Rust PopulationField survey · Rust servers
Observing 91,534 players 11,873 servers 3,854 with someone on 380 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,344habitat unknownfirst seen 13 Sep 2026

chilling_wave

Online 185.250.36.125:28015 checked 8m ago

moddedoxide

Measurements

Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,344
top 69%
Last wipe
55d ago
no schedule published
Next wipe
–
no wipe seen yet
Obs. 1 · sightings

Players

AveragePeak
0123416:0001:0010:0020:0005:0014:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

02040608016:0001:0010:0020:0005:0014:00

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does chilling_wave rank against other Rust servers?

Over the past week it ranks #15,344 for player hours, which puts chilling_wave in the top 69% of all ranked servers.

How busy is chilling_wave?

Of its 50 slots, chilling_wave is using 0 right now. Counted over seven days: an average of 0 players.

Lists and tags

What do the server tags on chilling_wave mean?

What the game's server browser reads from chilling_wave is this set of tags: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): You can join up to 50 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): Your game needs the same version, protocol 2633, to join; cs162929 (Build): The game build is 162929; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server has no region code; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.

Which Rust Population lists and filters include chilling_wave?

These Rust Population lists include chilling_wave: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Wipe notes

What is the wipe schedule on chilling_wave?

The record holds too few of chilling_wave's wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 55 days 13 hours ago.

Map and rules

Which map does chilling_wave run?

A procedural map of size 2,000 from seed 78955152, generated by the game, is in use on chilling_wave. Size and seed together fix the map, so you can view it on RustMaps from this page.

What are the rules and settings on chilling_wave?

No gather rate appears in the name of chilling_wave. No limit is set beyond the standard 8 players per group. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. You find it under Modded, since plugins or settings change how it plays. You will find Oxide running as plugins. The anti-cheat VAC from Valve is enabled.

Server details

Which version of Rust does chilling_wave run?

The setup is Rust network protocol 2633 and build 162929 on Linux for chilling_wave. Your game needs the same protocol to join; Steam takes care of updating it.

Does chilling_wave run smoothly?

In the last 48 hours, it averaged 54 server fps, with a low of 13. Entities peaked at 26,590, including buildings, deployables and everything else. Up to 1,050 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.

Is chilling_wave online, and how reliable is it?

chilling_wave is up and running at the moment. The uptime it reports suggests a restart roughly 3 hours ago. Over the last 7 full days, 167 of 168 hours were online, or 99%. It was first seen by Rust Population on 13 September 2026.

Where is chilling_wave located?

A region is not published by chilling_wave. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. Connect at 185.250.36.125:28015.

Getting in

How do I join chilling_wave?

Open the console with F1 in Rust and enter client.connect 185.250.36.125:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs162929,ts8,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players You can join up to 50 slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2633
Protocol Your game needs the same version, protocol 2633, to join.
cs162929
Build The game build is 162929.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code This server has no region code.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The game is changed by plugins or settings, so it is listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.