On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 750% full
7-day average0peak –
Rank#15,341top 69%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 75 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,341 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 177 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 216 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
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 22 Oct. 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
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 high risk solo/duo only sit?
You'll find no region listed by high risk solo/duo only. Rust Server Score takes the server's word for its location and does not trace the hardware. 23.109.125.138:27117 is the address to use.
How dependable is high risk solo/duo only, and is it online at the moment?
Right now, high risk solo/duo only is online. About 3 days 4 hours ago, it restarted, based on the uptime it reports. It was up 143 of 144 hours over the last 6 full days, which is 99% of the time. The first sighting by Rust Server Score was on 22 October 2026.
Does high risk solo/duo only perform well?
The average over the last 48 hours was 177 server fps, and it never went below 110. At its peak, it held 94,564 entities, including buildings, deployables and all else in the world. At its highest, it used 4,688 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is high risk solo/duo only on?
Rust network protocol 2635 and build 167781 on Linux is what high risk solo/duo only runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does high risk solo/duo only reset?
The record holds too few of high risk solo/duo only's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 25 days 13 hours.
Population
What position does high risk solo/duo only hold in the rankings?
In the top 69% of all ranked servers, high risk solo/duo only sits at #15,341 for player hours over the last seven days.
How many players does high risk solo/duo only usually have?
high risk solo/duo only is showing 0 players right now, with 75 slots in total. A seven-day average of 0 players applies here.
Tags
What is meant by the tags on high risk solo/duo only?
The game's browser takes its cue from the tags high risk solo/duo only has set: gmrust (Game mode): Rust survival, played by the standard rules; mp75 (Max players): Its slot count is 75; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs167781 (Build): The game build is 167781; 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. 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 lists and filters on Rust Server Score show high risk solo/duo only?
These Rust Server Score lists count high risk solo/duo only 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.
Server rules
Which rules does high risk solo/duo only enforce, and what are its settings?
Nothing in the name of high risk solo/duo only states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
high risk solo/duo only runs which map?
A procedural map of size 4,000 and seed 50000, generated by the game, is what high risk solo/duo only runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto high risk solo/duo only?
Enter client.connect 23.109.125.138:27117 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 asmp75,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp75
Max playersIts slot count is 75.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs167781
BuildThe game build is 167781.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).