Working its way up from the back of the class: #16,670 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
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
48/ 100
D
Slipped a little: down 559 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
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 70% of all ranked servers, and #207 of the solo servers (top 90%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Which region is Cosmic Competition Solo Compile Test based in?
No region is published for Cosmic Competition Solo Compile Test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 13.140.42.187:29725.
Is Cosmic Competition Solo Compile Test up, and how steady is its uptime?
The server is down: Cosmic Competition Solo Compile Test is offline now, with the last sighting 28 days 15 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 1 October 2026.
What Rust version is Cosmic Competition Solo Compile Test on?
The server Cosmic Competition Solo Compile Test is on Rust network protocol 2633 and build 165217 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Cosmic Competition Solo Compile Test reset?
Cosmic Competition Solo Compile Test has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 28 days 15 hours.
Player count
Where does Cosmic Competition Solo Compile Test place in the wider field of Rust servers?
In the top 70% of all ranked servers, Cosmic Competition Solo Compile Test sits at #16,670 for player hours over the last seven days. It comes #207 among servers in the solo group.
How many players does Cosmic Competition Solo Compile Test usually have?
It has been 28 days 15 hours since Cosmic Competition Solo Compile Test was last seen, and it is offline right now.
Tags and filters
What do Cosmic Competition Solo Compile Test's tags stand for?
You'll see Cosmic Competition Solo Compile Test tagged with gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): The server holds 1 slots; ts1 (Group limit): A team can hold 1 players at most; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $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): Plugin framework: Carbon 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 Cosmic Competition Solo Compile Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Cosmic Competition Solo Compile Test among them: Modded Rust servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Solo.
Server rules
What settings and rules apply on Cosmic Competition Solo Compile Test?
The name of Cosmic Competition Solo Compile Test gives no gather rate. Solo play only, with no teams permitted. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Cosmic Competition Solo Compile Test uses?
A procedural map, generated by the game, is what Cosmic Competition Solo Compile Test runs.
Getting in
How should you connect to Cosmic Competition Solo Compile Test?
Enter client.connect 13.140.42.187:29725 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 asmp1,ptrak,$r?,v2633,gmrust,cs165217,ts1,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersThe server holds 1 slots.
ts1
Group limitA team can hold 1 players at most.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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
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 momentum (D); standing is the one to work on (F).