A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,373 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
28/ 100
F
Lost ground: down 6,700 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
16 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
····W··
·WWWW·W
W······
W·W·W··
WWW····
·W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 21 OctTue 20 OctTue 20 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 12:44 UTC1d ago
–
–
running
1
Wed 21 Oct, 08:38 UTC7d ago
1
–
6.2 days
0
Tue 20 Oct, 19:10 UTC7d ago
1
–
0.6 days
0
Tue 20 Oct, 07:55 UTC8d ago
1
–
0.5 days
0
Mon 19 Oct, 14:34 UTC9d ago
1
–
0.7 days
1
Fri 16 Oct, 10:43 UTC12d ago
1
–
3.2 days
0
Wed 14 Oct, 09:08 UTC14d ago
1
–
2.1 days
1
Mon 12 Oct, 07:32 UTC16d ago
1
–
2.1 days
1
Mon 5 Oct, 22:50 UTC22d ago
1
–
6.4 days
0
Mon 5 Oct, 16:27 UTC23d ago
1
–
0.3 days
0
Sun 4 Oct, 15:16 UTC24d ago
1
–
1 days
0
Fri 2 Oct, 15:22 UTC26d ago
0
–
2 days
0
Thu 1 Oct, 10:02 UTC27d ago
0
–
1.2 days
1
Wed 30 Sep, 09:25 UTC28d ago
1
–
1 days
1
Tue 29 Sep, 10:47 UTC29d ago
1
–
0.9 days
0
Fri 25 Sep, 09:43 UTC33d ago
0
–
4 days
1
Fri 18 Sep, 15:59 UTC40d ago
1
–
6.7 days
1
Thu 17 Sep, 10:13 UTC41d ago
1
–
1.2 days
0
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
In what location does cipeaX Staging Test Server sit?
You'll find no region listed by cipeaX Staging Test Server. Rust Server Score takes the server's word for its location and does not trace the hardware. 95.91.211.106:28015 is the address to use.
Is cipeaX Staging Test Server up, and how steady is its uptime?
The server is down: cipeaX Staging Test Server is offline now, with the last sighting 30 hours ago. It was up 2% of the time over the last 7 full days, 3 of 168 hours. On 15 September 2026, Rust Server Score saw it for the first time.
Which Rust version is cipeaX Staging Test Server running?
Rust network protocol 2635 and build 169310 on Windows is what cipeaX Staging Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does cipeaX Staging Test Server wipe its map?
cipeaX Staging Test Server wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 30 hours have passed since this world was made.
What should you expect from wipe day on cipeaX Staging Test Server?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does cipeaX Staging Test Server place in the wider field of Rust servers?
Over the last seven days, cipeaX Staging Test Server has #15,373 for player hours, in the top 69% of all ranked servers.
Is cipeaX Staging Test Server a busy server?
cipeaX Staging Test Server is offline at the moment; the last time it was seen was 30 hours ago. A seven-day average of 0 players applies here.
Lists and filters
What is meant by the tags on cipeaX Staging Test Server?
The game's browser takes its cue from the tags cipeaX Staging Test Server has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs169310 (Build): The game build is 169310; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show cipeaX Staging Test Server?
These Rust Server Score lists count cipeaX Staging Test Server among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Map and rules
What settings and rules apply on cipeaX Staging Test Server?
The name of cipeaX Staging Test Server gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Connecting
What is the way to join cipeaX Staging Test Server?
Enter client.connect 95.91.211.106:28015 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 asmp10,ptrak,$r?,v2635,gmrust,cs169310,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs169310
BuildThe game build is 169310.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under 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 term to build on. Strongest in standing (F); population is the one to work on (F).