On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#13,773top 62%
Last wipe4d agoweekly schedule
Next wipe2d 4hFri 30 Oct, 15:09 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
38/ 100
F
Working its way up from the back of the class: #13,773 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
85/ 100
A−
Mostly smooth: 51 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
28/ 100
F
Lost ground: down 6,024 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·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 Friday 30 October, 15:09 UTC, in 2d 4h.
Its weekly schedule tag · low confidence
usual gap6.8 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
crowd held33%else halves by day 1.5
Coming wipes
2d 4hFri 30 Oct, 15:09 UTC
8d 8hThu 5 Nov, 19:00 UTCFW
9d 4hFri 6 Nov, 15:09 UTC
16d 4hFri 13 Nov, 15:09 UTC
23d 4hFri 20 Nov, 15:09 UTC
30d 4hFri 27 Nov, 15:09 UTC
36d 8hThu 3 Dec, 19:00 UTCFW
37d 4hFri 4 Dec, 15:09 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 15:09 UTC4d ago
0
–
running
0
Fri 16 Oct, 15:08 UTC11d ago
2
halved by day 2
7 days
0
Fri 9 Oct, 19:53 UTC18d ago
2
halved by day 1
6.8 days
0
Tue 6 Oct, 16:02 UTC21d ago
1
✓ held half
3.2 days
1
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
Where in the world is 5X | ZemeRustu.cz | Solo Only?
No region is published for 5X | ZemeRustu.cz | Solo Only. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 31.97.122.1:28015.
Is 5X | ZemeRustu.cz | Solo Only up, and how steady is its uptime?
You can join now: 5X | ZemeRustu.cz | Solo Only is online. The uptime it reports puts the last restart at about 5 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 4 October 2026.
How well does 5X | ZemeRustu.cz | Solo Only run?
The average over the last 48 hours was 51 server fps, and it never went below 18. At its peak, it held 54,092 entities, including buildings, deployables and all else in the world. At its highest, it used 2,223 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does 5X | ZemeRustu.cz | Solo Only sit?
Rust network protocol 2635 and build 168909 on Linux is what 5X | ZemeRustu.cz | Solo Only runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does 5X | ZemeRustu.cz | Solo Only wipe, and how often?
Its tag sets the prediction, as the record holds too few of 5X | ZemeRustu.cz | Solo Only's wipes to confirm its schedule. Friday 30 October at 15:09 UTC is the date set for its next wipe. 4 days 19 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on 5X | ZemeRustu.cz | Solo Only when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 33% of its recent wipes. In the other wipes it slipped under half by day 1.5.
Population
Where does 5X | ZemeRustu.cz | Solo Only place in the wider field of Rust servers?
In the top 62% of all ranked servers, 5X | ZemeRustu.cz | Solo Only sits at #13,773 for player hours over the last seven days.
Is 5X | ZemeRustu.cz | Solo Only a busy server?
5X | ZemeRustu.cz | Solo Only is showing 0 players right now, with 50 slots in total. It peaked at 1 and averaged 0 players over the last seven days.
Tags and filters
How should you read the tags on 5X | ZemeRustu.cz | Solo Only?
The game's browser takes its cue from the tags 5X | ZemeRustu.cz | Solo Only has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature 5X | ZemeRustu.cz | Solo Only?
These Rust Server Score lists count 5X | ZemeRustu.cz | Solo Only among them: 5x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 5x.
Map and rules
How is 5X | ZemeRustu.cz | Solo Only set up, and what rules does it keep?
Going by its name, 5X | ZemeRustu.cz | Solo Only runs 5x gather. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
5X | ZemeRustu.cz | Solo Only runs which map?
A procedural map of size 3,000 and seed 20261004, generated by the game, is what 5X | ZemeRustu.cz | Solo Only runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto 5X | ZemeRustu.cz | Solo Only?
Enter client.connect 31.97.122.1:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://zemerustu.cz.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^z,^y,^w,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).