Working its way up from the back of the class: #13,634 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
43/ 100
F
Slipped a little: down 1,964 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 62% of all ranked servers. 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
In what location does Liam 8x Solo + Bots (private) sit?
No region is published for Liam 8x Solo + Bots (private). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 86.175.210.108:28015.
How dependable is Liam 8x Solo + Bots (private), and is it online at the moment?
At this moment, Liam 8x Solo + Bots (private) is offline; the last time it was seen was 20 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 9 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Liam 8x Solo + Bots (private) sit?
Rust network protocol 2634 and build 167231 on Windows is what Liam 8x Solo + Bots (private) runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Liam 8x Solo + Bots (private) reset?
Liam 8x Solo + Bots (private) has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 20 days 7 hours.
Population
What position does Liam 8x Solo + Bots (private) hold in the rankings?
In the top 62% of all ranked servers, Liam 8x Solo + Bots (private) sits at #13,634 for player hours over the last seven days.
What does the population on Liam 8x Solo + Bots (private) look like?
It has been 20 days 3 hours since Liam 8x Solo + Bots (private) was last seen, and it is offline right now.
Lists and filters
How should you read the tags on Liam 8x Solo + Bots (private)?
The game's browser takes its cue from the tags Liam 8x Solo + Bots (private) has set: gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): Its slot count is 4; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): Build number: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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. 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 Liam 8x Solo + Bots (private)?
These Rust Server Score lists count Liam 8x Solo + Bots (private) among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is Liam 8x Solo + Bots (private) set up, and what rules does it keep?
Going by its name, Liam 8x Solo + Bots (private) runs 8x gather. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Liam 8x Solo + Bots (private) uses?
A procedural map, generated by the game, is what Liam 8x Solo + Bots (private) runs.
Getting in
How do you get onto Liam 8x Solo + Bots (private)?
To connect, start Rust, press F1, and type client.connect 86.175.210.108:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max playersIts slot count is 4.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildBuild number: 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.
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. Even marks across the subjects, from F to F.