Online 78.24.41.96:28025 checked 9m ago
CRYMAP_TEST
Connect
srv = rust.server("78.24.41.96:28026")
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 best
Top 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 16h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 20h | Tue 10 Nov, 22:55 UTC | wipe |
| 2 | 27d 20h | Tue 24 Nov, 22:55 UTC | wipe |
| 3 | 36d 16h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 20h | Tue 8 Dec, 22:55 UTC | wipe |
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 · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 22:55 UTC3h ago | NaN | NaN | running | 3 |
| 1 | Sun 18 Oct, 12:14 UTC9d ago | 2 | halved by day 5 | 9.4 days | 0 |
| 2 | Wed 14 Oct, 22:19 UTC13d ago | 3 | halved by day 1 | 3.6 days | 0 |
| 3 | Thu 8 Oct, 18:48 UTC19d ago | 3 | held half | 6.1 days | 2 |
| 4 | Tue 6 Oct, 22:30 UTC21d ago | 3 | NaN | 1.8 days | 0 |
| 5 | Sat 3 Oct, 19:27 UTC24d ago | 1 | held half | 3.1 days | 1 |
| 6 | Thu 1 Oct, 17:57 UTC FW26d ago | 3 | held half | 2.1 days | 2 |
| 7 | Wed 30 Sep, 20:18 UTC27d ago | 3 | NaN | 0.9 days | 3 |
| 8 | Fri 18 Sep, 09:06 UTC39d ago | 3 | halved by day 1 | 12.5 days | 2 |
| 9 | 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.
display(srv.map, srv.info())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 可爱-1000倍PVE-不掉-突袭-养殖-僵尸-无限耐久 | EA · groups of 8+ · biweekly · 1 on average | 1/100 |
| 1 | [EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | EU · groups of 8+ · 112 on average | 70/999 |
| 2 | [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 88 on average | 162/999 |
| 3 | [AU] Rusticated.com - Creative Sandbox | Build | Never Wipes | OC · groups of 8+ · 51 on average | 49/150 |
| 4 | Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA | EU · groups of 30+ · weekly · 35 on average | 13/100 |
| 5 | AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 23 on average | 3/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does CRYMAP_TEST rank?
Over the last seven days CRYMAP_TEST sits at #4,460 on player hours, in the top 20% of ranked servers.
What population does CRYMAP_TEST carry?
Current row: 0 players on CRYMAP_TEST, against 20 slots. Over the last seven days it averaged 1 players and peaked at 5. Averaged by hour over 48 hours, 16:00 UTC is the busiest, at 3 players.
Server facts
How well does CRYMAP_TEST perform?
The 48-hour average is 193 server fps, with a low of 183. Buildings, deployables and all else in the world took the count as high as 30,648 entities. The memory field tops out at 2,515 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does CRYMAP_TEST run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by CRYMAP_TEST. Joining needs the same protocol on your game; Steam handles the update.
Is CRYMAP_TEST up, and what does its uptime show?
Online is the state at the latest refresh for CRYMAP_TEST. Count back 1 hours from its reported uptime to get the last restart. 126 of 168 hours up over the last 7 full days, or 75%. Rust Data logged it first on 13 September 2026.
Where does CRYMAP_TEST sit?
No region is published by CRYMAP_TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. 78.24.41.96:28025 is its address.
Settings and map
Which settings and rules does CRYMAP_TEST run?
You will not find a gather rate in the string CRYMAP_TEST. The group limit sits at the default of 8 players. Recorded as build & creative, no gathering, just sandbox building. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. VAC is running: Valve's anti-cheat is on.
What is the map on CRYMAP_TEST?
Size 2,500, seed 1337: the procedural map on CRYMAP_TEST, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipe schedule
On what schedule does CRYMAP_TEST wipe?
The prediction follows the tag, because CRYMAP_TEST's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 3 hours ago. Its tags carry a wipe schedule of every two weeks.
What is wipe day on CRYMAP_TEST like?
The average peak over recent wipes is 3 players. 25 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 3.
Tags and filters
Where does CRYMAP_TEST appear among Rust Data lists and filters?
These Rust Data lists include CRYMAP_TEST: Modded Rust servers, Servers with build or creative tags and Rust creative servers, listed. It appears under these filters 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 24 hours.
How should you read the server tags on CRYMAP_TEST?
Read by the game's server browser, the tags CRYMAP_TEST publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^c (Creative): Build freely, with no gathering: sandbox mode; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join CRYMAP_TEST?
Enter client.connect 78.24.41.96:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.