Working its way up from the back of the class: #14,850 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
52/ 100
D
Moving up: up 510 places this week.
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 65% of all ranked servers, top 84% in EU. 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
Next wipe Friday 30 October, 13:03 UTC, in 16h.
Weekly: 7 days after its last 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
The EU tag on Solo | Silo X1 NOLIMIT puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 46.146.235.188:28015.
Is Solo | Silo X1 NOLIMIT up, and how steady is its uptime?
The server is down: Solo | Silo X1 NOLIMIT is offline now, with the last sighting 27 days 6 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 2 October 2026, Rust Server Score saw it for the first time.
What Rust version is Solo | Silo X1 NOLIMIT on?
You will find Solo | Silo X1 NOLIMIT on Rust network protocol 2634 and build 166586, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Solo | Silo X1 NOLIMIT wipe its map?
weekly: 7 days after its last wipe gives the basis for estimating Solo | Silo X1 NOLIMIT's next wipe. It is due to wipe next on Friday 30 October at 13:03 UTC. The world it runs now was created 27 days 7 hours. Its tags state that it wipes weekly.
Player count
Where does Solo | Silo X1 NOLIMIT place in the wider field of Rust servers?
Over the last seven days, Solo | Silo X1 NOLIMIT has #14,850 for player hours, in the top 65% of all ranked servers and #2,414 in Europe.
How many players does Solo | Silo X1 NOLIMIT usually have?
It has been 27 days 6 hours since Solo | Silo X1 NOLIMIT was last seen, and it is offline right now.
Tags
How should you read the tags on Solo | Silo X1 NOLIMIT?
The game's browser takes its cue from the tags Solo | Silo X1 NOLIMIT has set: gmrust (Game mode): Rust survival, played by the standard rules; mp30 (Max players): 30 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166586 (Build): The game build is 166586; ptsw (Networking): 'sw' is the network layer here; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EU (Europe): The server browser lists it under Europe. 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 Solo | Silo X1 NOLIMIT?
These Rust Server Score lists count Solo | Silo X1 NOLIMIT among them: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 1x.
Rules and settings
What settings and rules apply on Solo | Silo X1 NOLIMIT?
Solo | Silo X1 NOLIMIT sets gather at 1x, as its name suggests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in 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 Oxide. Vanilla is what it calls itself: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Solo | Silo X1 NOLIMIT uses?
Solo | Silo X1 NOLIMIT runs a procedural map, which the game generates.
Connecting
How should you connect to Solo | Silo X1 NOLIMIT?
Enter client.connect 46.146.235.188: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 asmp30,ptsw,$r?,v2634,^w,^v,EU,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp30
Max players30 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166586
BuildThe game build is 166586.
ptsw
Networking'sw' is the network layer here.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EU
EuropeThe server browser lists it under Europe.
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).