CRYMAP_TEST
Online 78.24.41.96:28025 checked 18m ago
Measurements
Players
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
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 8d 1h. The force wipe · high confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 25 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 22:55 UTC18h ago | – | – | running | 3 |
| Sun 18 Oct, 12:14 UTC10d ago | 2 | halved by day 5 | 9.4 days | 0 |
| Wed 14 Oct, 22:19 UTC13d ago | 3 | halved by day 1 | 3.6 days | 0 |
| Thu 8 Oct, 18:48 UTC19d ago | 3 | held half | 6.1 days | 2 |
| Tue 6 Oct, 22:30 UTC21d ago | 3 | – | 1.8 days | 0 |
| Sat 3 Oct, 19:27 UTC24d ago | 1 | held half | 3.1 days | 1 |
| Thu 1 Oct, 17:57 UTC FW26d ago | 3 | held half | 2.1 days | 2 |
| Wed 30 Sep, 20:18 UTC27d ago | 3 | – | 0.9 days | 3 |
| Fri 18 Sep, 09:06 UTC40d ago | 3 | halved by day 1 | 12.5 days | 2 |
| Mon 14 Sep, 18:17 UTC43d ago | 3 | halved by day 1 | 3.6 days | 3 |
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.
Quick answers
Population
How does CRYMAP_TEST rank against other Rust servers?
The last seven days of player hours place CRYMAP_TEST at #4,495, within the top 20% of all ranked servers.
How busy is CRYMAP_TEST?
The count reads 3 players on CRYMAP_TEST, which has 20 slots. We counted an average of 1 players in the past week, with 5 at the busiest. In the last 48 hours the peak hour came at 16:00 UTC, averaging 3 players.
Lists and tags
What do the server tags on CRYMAP_TEST mean?
What the game's server browser reads from CRYMAP_TEST is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): The server has 20 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): Game build: 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): Facepunch's game, unaltered: no kits, no rate changes, no extra rules; ^c (Creative): No gathering is needed; this is sandbox building where you build what you like; ^z (Modded): This server appears under Modded because plugins or settings alter the game; ^y (Carbon): Carbon provides the plugin framework here. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include CRYMAP_TEST?
On Rust Population, CRYMAP_TEST is filed under these lists: Modded Rust servers, counted, Build and creative servers and Rust creative servers, counted live. These are the filters it appears under when you browse the list: Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Creative ^c, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Wipe notes
What does wipe day look like on CRYMAP_TEST?
The busiest point of its recent wipes averaged 3 players. 25 hours after the latest wipe the crowd peaked. Half that peak held until the next wipe in 50% of its recent wipes. The crowd dropped below half by day 3 when it did not hold.
What is the wipe schedule on CRYMAP_TEST?
Its tag sets the prediction: too few of CRYMAP_TEST's wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 18 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.
Settings
Which map does CRYMAP_TEST run?
CRYMAP_TEST uses a map the game generates, procedural, at size 2,500 with seed 1337. You can look at it on RustMaps from this page: size and seed determine the map. You will see the map named Custom Map.
What are the rules and settings on CRYMAP_TEST?
Nothing in CRYMAP_TEST's name says how gather works. No limit is set beyond the standard 8 players per group. build & creative is what it runs, no gathering; build in a sandbox. You find it under Modded, since plugins or settings change how it plays. Carbon plugins are in use here. By its own description it is vanilla: facepunch's game, unaltered: no kits, no rate changes, no extra rules. The anti-cheat VAC from Valve is enabled.
About the server
Which version of Rust does CRYMAP_TEST run?
The setup is Rust network protocol 2635 and build 168909 on Linux for CRYMAP_TEST. Your game needs the same protocol to join; Steam takes care of updating it.
Does CRYMAP_TEST run smoothly?
The last 48 hours saw an average of 193 server fps, with 183 as the lowest. The entity count reached 30,648: buildings, deployables and all other objects. Memory use peaked at 2,515 MB. Lag, as players feel it, is low fps combined with a climbing entity count.
Is CRYMAP_TEST online, and how reliable is it?
Right now, CRYMAP_TEST is online. About 16 hours ago, it restarted, according to its uptime. It was up 75% of the time over the last 7 full days, 126 out of 168 hours. It was first seen by Rust Population on 13 September 2026.
Where is CRYMAP_TEST located?
A region is not published by CRYMAP_TEST. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 78.24.41.96:28025.
How to join
How do I join CRYMAP_TEST?
To connect directly, open Rust's console with F1 and type client.connect 78.24.41.96:28025; or press Launch Rust on this page and Steam opens Rust and joins for you.