Working its way up from the back of the class: #15,339 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
22/ 100
F
Lost ground: down 8,661 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
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.
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 21 Sep. 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, and #198 of the solo servers (top 90%). Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W···W·
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap3.7 daysbetween real wipes
wipe-day peak3players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Sat 3 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 29 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 10:46 UTC25d ago
3
–
running
0
Tue 29 Sep, 17:47 UTC29d ago
3
halved by day 2
3.7 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
No region is published for ASTRO | Rust Solo x10. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 194.87.209.146:20211.
How dependable is ASTRO | Rust Solo x10, and is it online at the moment?
The server is down: ASTRO | Rust Solo x10 is offline now, with the last sighting 7 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 21 September 2026, Rust Server Score saw it for the first time.
Which Rust version is ASTRO | Rust Solo x10 running?
Rust network protocol 2634 and build 166652 on Linux is what ASTRO | Rust Solo x10 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does ASTRO | Rust Solo x10 wipe its map?
There are too few wipes on record for ASTRO | Rust Solo x10 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 25 days 23 hours have passed since this world was made.
What happens on ASTRO | Rust Solo x10 when wipe day arrives?
The average peak on its recent wipes was 3 players. 29 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 2 in the wipes where it did not hold.
Player numbers
Where does ASTRO | Rust Solo x10 place in the wider field of Rust servers?
Over the last seven days, ASTRO | Rust Solo x10 has #15,339 for player hours, in the top 69% of all ranked servers. In the solo group, it ranks #198.
What does the population on ASTRO | Rust Solo x10 look like?
ASTRO | Rust Solo x10 is offline at the moment; the last time it was seen was 7 days 12 hours ago.
Lists and filters
How should you read the tags on ASTRO | Rust Solo x10?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts1 (Group limit): A team can hold 1 players at most; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags ASTRO | Rust Solo x10 publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature ASTRO | Rust Solo x10?
Rust Server Score lists that include ASTRO | Rust Solo x10: 10x Rust servers, graded, 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 Oxide ^o; Group limit: Solo; Gather rate: 10x.
Map and rules
How is ASTRO | Rust Solo x10 set up, and what rules does it keep?
ASTRO | Rust Solo x10 sets gather at 10x, as its name suggests. Solo play only, with no teams permitted. It runs survival, 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 Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map ASTRO | Rust Solo x10 uses?
ASTRO | Rust Solo x10 runs a game-generated procedural map at size 3,500, seed 1982554169. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join ASTRO | Rust Solo x10?
Enter client.connect 194.87.209.146:20211 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://astro-rust.gamestores.app/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs166652,ts1,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts1
Group limitA team can hold 1 players at most.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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); wipes are the one to work on (F).