On the class lists: C (61), with population over 48 hours and no performance mark.
Players now3/ 506% full
7-day average2peak 6
Rank#3,571top 16% · #589 in NA
No wipesresets5 new worlds this week: a reset every few hours, not a wipe schedule
Next wipe–resets, no wipes
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
3/ 100
F
A quiet classroom so far: 2 of 50 on average. Plenty of space to grow.
Standingrank on player hours
84/ 100
B+
Holds a respectable place: #3,571 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
42/ 100
F
Needs to work on its frame rate: 25 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
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
Strongest in uptime (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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 16% of all ranked servers, top 32% in NA, and #215 of the duo servers (top 51%). Ranked on player hours over the last seven days.
Attendance: the wipe record
a new world every few hours
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WW·W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
World resets
a new world every few hours; none of these counts as a wipe
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 03:08 UTC16h ago
–
–
–
5
Tue 27 Oct, 02:04 UTC2d ago
–
–
–
2
Mon 26 Oct, 18:34 UTC3d ago
–
–
–
2
Mon 26 Oct, 18:02 UTC3d ago
–
–
–
2
Mon 26 Oct, 17:21 UTC3d ago
4
–
0.4 days
0
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In North America, according to its own listing, sits k1 solo duo, with the NA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 66.51.98.66:28000.
Is k1 solo duo up, and how steady is its uptime?
The server is up: k1 solo duo is online now. About 14 hours ago, it restarted, based on the uptime it reports. It was up 98% of the time over the last 2 full days, 47 of 48 hours. The first sighting by Rust Server Score was on 26 October 2026.
Does k1 solo duo perform well?
The average over the last 48 hours was 25 server fps, and it never went below 5. Up to 72,885 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 2,628 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is k1 solo duo on?
Rust network protocol 2635 and build 168909 on Linux is what k1 solo duo runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does k1 solo duo wipe, and how often?
None of the resets on k1 solo duo is a wipe: the world is remade every few hours and no schedule is kept.
Population
Where does k1 solo duo place in the wider field of Rust servers?
In North America, k1 solo duo is #589, and overall it is #3,571 on player hours over the last seven days, in the top 16% of all ranked servers. It comes #215 among servers in the duo group.
Is k1 solo duo a busy server?
Right now, 3 players are on k1 solo duo, which has 50 slots. The seven-day average is 2 players, with a peak of 6. Over the last 48 hours, the peak hour was 04:00 UTC, averaging 5 players.
Tags and filters
What is meant by the tags on k1 solo duo?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts2 (Group limit): A team can hold 2 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Oxide (uMod) provides the plugin framework here; NA (North America): You will find it under North America in the browser are the tags k1 solo duo 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 k1 solo duo?
These Rust Server Score lists count k1 solo duo among them: Duo servers, marked like a report, Best community servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m and Oxide ^o; Group limit: Duo; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
Rules and settings
What settings and rules apply on k1 solo duo?
Nothing in the name of k1 solo duo states a gather rate. The cap on group size is 2 players (duo). You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on k1 solo duo?
The game generates the procedural map on k1 solo duo at size 3,500 with seed 1050612817. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to k1 solo duo?
Enter client.connect 66.51.98.66:28000 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 asmp50,ptrak,$r?,v2635,^m,NA,gmrust,cs168909,ts2,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts2
Group limitA team can hold 2 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
NA
North AmericaYou will find it under North America in the browser.
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 uptime (A+); population is the one to work on (F).