On the class lists: C (63), with population over 48 hours and no performance mark.
Players now3/ 2015% full
7-day average0peak 5
Rank#4,696top 21%
Last wipe9d agobiweekly schedule
Next wipe4d 15hSun 1 Nov, 12:14 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
79/ 100
B
Holds a respectable place: #4,696 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 192 server fps on average.
Wipeskeeping the crowd after a wipe
75/ 100
B
Holds its players well after a wipe: 75% of wipes kept half their crowd.
Momentumrank now against a week ago
63/ 100
C
Moving up: up 1,237 places this week.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 21% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W···W··
·······
··WF·W·
·W·W···
··W···W
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Sunday 1 November, 12:14 UTC, in 4d 15h.
Its biweekly schedule tag · low confidence
usual gap3.4 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak3players, last three wipes
crowd held75%else halves by day 1
Coming wipes
4d 15hSun 1 Nov, 12:14 UTC
8d 21hThu 5 Nov, 19:00 UTCFW
18d 15hSun 15 Nov, 12:14 UTC
32d 15hSun 29 Nov, 12:14 UTC
36d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 18 OctWed 14 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 25 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 18 Oct, 12:14 UTC9d ago
2
–
running
0
Wed 14 Oct, 22:19 UTC12d 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 UTC20d 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 UTCFW26d 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 UTC39d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
CRYMAP_TEST leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 78.24.41.96:28025.
How dependable is CRYMAP_TEST, and is it online at the moment?
You can join now: CRYMAP_TEST is online. About 2 days 3 hours ago, it restarted, based on the uptime it reports. It was up 75% of the time over the last 7 full days, 126 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does CRYMAP_TEST perform well?
It averaged 192 server fps over the last 48 hours, with a low of 183. At its peak, it held 30,648 entities, including buildings, deployables and all else in the world. Up to 2,341 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is CRYMAP_TEST on?
You will find CRYMAP_TEST on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does CRYMAP_TEST reset?
The prediction follows its tag, because too few of CRYMAP_TEST's wipes are on record to confirm the schedule. It is due to wipe next on Sunday 1 November at 12:14 UTC. It has been running its current world for 9 days 8 hours. Its tags give a wipe schedule of every two weeks.
What happens on CRYMAP_TEST when wipe day arrives?
The average peak on its recent wipes was 3 players. 25 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 75% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does CRYMAP_TEST place in the wider field of Rust servers?
In the top 21% of all ranked servers, CRYMAP_TEST sits at #4,696 for player hours over the last seven days.
How many players does CRYMAP_TEST usually have?
Right now, 3 players are on CRYMAP_TEST, which has 20 slots. It peaked at 5 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 16:00 UTC, with an average of 3 players.
Tags and filters
What do CRYMAP_TEST's tags stand for?
You'll see CRYMAP_TEST tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^c (Creative): No gathering here: it is a sandbox where you build what you want; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does CRYMAP_TEST appear in the Rust Server Score lists and filters?
Rust Server Score lists that include CRYMAP_TEST: Modded Rust servers, graded, Rust build and creative servers and Rust creative servers, scored and graded. These filters bring it up on the server 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 2 weeks.
Rules and settings
Which rules does CRYMAP_TEST enforce, and what are its settings?
Nothing in the name of CRYMAP_TEST states a gather rate. The group limit stays at the game's default of 8 players. You get build & creative here, no gathering, just sandbox building. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
Can you tell me which map CRYMAP_TEST uses?
CRYMAP_TEST runs a game-generated procedural map at size 2,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Connecting
How should you connect to CRYMAP_TEST?
Enter client.connect 78.24.41.96:28025 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,^z,^y,^b,^v,^c,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Gameplay
^c
CreativeNo gathering here: it is a sandbox where you build what you want.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework here.
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.
A steady term. Strongest in performance (A+); population is the one to work on (F).