On the class lists: C− (57), with population over 48 hours and no performance mark.
Players now0/ 150% full
7-day average0peak 1
Rank#5,773top 26%
Last wipe6d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 15 on average. Plenty of space to grow.
Standingrank on player hours
74/ 100
B−
Holds a respectable place: #5,773 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
67/ 100
C+
Slows down under load at times: 40 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.
AveragePeakWipe
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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 26% 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
No region is published for JP_Solo/Duo. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 163.44.98.246:28015.
Is JP_Solo/Duo up, and how steady is its uptime?
You can join now: JP_Solo/Duo is online. About 6 days 9 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 5 full days, 119 of 120 hours. The first sighting by Rust Server Score was on 23 October 2026.
Does JP_Solo/Duo perform well?
The average over the last 48 hours was 40 server fps, and it never went below 23. Up to 116,363 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 4,833 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does JP_Solo/Duo sit?
Rust network protocol 2635 and build 168909 on Linux is what JP_Solo/Duo runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does JP_Solo/Duo wipe, and how often?
The record holds too few of JP_Solo/Duo's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 6 days 10 hours have passed since this world was made.
Population
What position does JP_Solo/Duo hold in the rankings?
In the top 26% of all ranked servers, JP_Solo/Duo sits at #5,773 for player hours over the last seven days.
How many players does JP_Solo/Duo usually have?
JP_Solo/Duo is showing 0 players right now, with 15 slots in total. It peaked at 1 and averaged 0 players over the last seven days.
Lists and filters
What is meant by the tags on JP_Solo/Duo?
You'll see JP_Solo/Duo tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does JP_Solo/Duo appear in the Rust Server Score lists and filters?
These Rust Server Score lists count JP_Solo/Duo 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; Last wipe: In the last week.
Map and rules
How is JP_Solo/Duo set up, and what rules does it keep?
The name of JP_Solo/Duo gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, 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. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on JP_Solo/Duo?
JP_Solo/Duo runs a game-generated procedural map at size 4,500, seed 85804905. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join JP_Solo/Duo?
Enter client.connect 163.44.98.246: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 asmp15,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp15
Max playersThe server holds 15 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is 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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).