On the class lists: F (32), with population over 48 hours and no performance mark.
Players now1/ 333% full
7-day average1peak 3
Rank#7,131top 32%
Last wipe11d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
42/ 100
F
Room for more players: 1 of 3 on average.
Standingrank on player hours
68/ 100
C+
Working its way up from the back of the class: #7,131 on player hours.
Uptimehours on the list, last 48
15/ 100
F
Attendance needs work: on the list only 7 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 189 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 797 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); wipes are 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.
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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 32% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W··W··
···WW··
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.7 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 4
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 07:14 UTC11d ago
1
–
running
1
Thu 15 Oct, 08:59 UTC12d ago
1
–
0.9 days
1
Fri 9 Oct, 07:44 UTC18d ago
3
halved by day 4
6.1 days
2
Tue 6 Oct, 15:09 UTC21d ago
3
–
2.7 days
1
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
You'll find no region listed by NAKA server solo. Rust Server Score takes the server's word for its location and does not trace the hardware. 112.136.34.226:28015 is the address to use.
Is NAKA server solo up, and how steady is its uptime?
You cannot join now: NAKA server solo is offline, last seen 3 hours ago. According to its reported uptime, the last restart was about 51 minutes ago. For the last 7 full days, it was up 13 of 168 hours, or 8% of the time. On 21 September 2026, Rust Server Score saw it for the first time.
Is NAKA server solo smooth to play on?
It never fell below 183 server fps in the last 48 hours, averaging 189. At its peak, it held 95,183 entities, including buildings, deployables and all else in the world. Up to 1,867 MB of memory was used. Players feel lag when fps drops and entities pile up.
What Rust version is NAKA server solo on?
You will find NAKA server solo on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does NAKA server solo wipe, and how often?
No next wipe can be predicted for NAKA server solo, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 11 days 11 hours have passed since this world was made.
What happens on NAKA server solo when wipe day arrives?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 1 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Population
Where does NAKA server solo sit among Rust servers?
In the top 32% of all ranked servers, NAKA server solo sits at #7,131 for player hours over the last seven days.
Is NAKA server solo a busy server?
The last sighting of NAKA server solo was 3 hours ago, and it is offline right now. The seven-day average is 1 players, with a peak of 3. Over the last 48 hours, the peak hour was 12:00 UTC, averaging 1 players.
Lists and filters
How should you read the tags on NAKA server solo?
You'll see NAKA server solo tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp3 (Max players): Its slot count is 3; 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): Plugin framework: 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.
Which lists and filters on Rust Server Score show NAKA server solo?
These Rust Server Score lists count NAKA server solo 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 2 weeks.
Server rules
Which rules does NAKA server solo enforce, and what are its settings?
The name of NAKA server solo gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
NAKA server solo runs which map?
A procedural map of size 4,000 and seed 1, generated by the game, is what NAKA server solo runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto NAKA server solo?
To connect, start Rust, press F1, and type client.connect 112.136.34.226:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp3
Max playersIts slot count is 3.
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
OxidePlugin framework: 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 term to build on. Strongest in performance (A+); wipes are the one to work on (F).