On the class lists: D (53), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#8,005top 36%
Last wipe4d agono schedule published
Next wipe–too few wipes 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 50 on average. Plenty of space to grow.
Standingrank on player hours
64/ 100
C
Working its way up from the back of the class: #8,005 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: 199 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 steady term.
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
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 24 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 36% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 12:39 UTC4d ago
2
–
running
0
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
NaGiNaGI leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 64.31.11.27:28080 is the address to use.
How reliable is NaGiNaGI, and is it up?
You can join now: NaGiNaGI is online. The uptime it reports puts the last restart at about 18 hours ago. It was up 100% of the time over the last 3 full days, 72 of 72 hours. It was first seen by Rust Server Score on 24 October 2026.
Is NaGiNaGI smooth to play on?
It averaged 199 server fps over the last 48 hours, with a low of 124. Buildings, deployables and everything else in the world added up to as many as 32,534 entities. Up to 1,791 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is NaGiNaGI on?
Rust network protocol 2635 and build 168909 on Windows is what NaGiNaGI runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does NaGiNaGI reset?
The record holds too few of NaGiNaGI'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. 4 days 7 hours have passed since this world was made.
What happens on NaGiNaGI when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 2 hours into the latest wipe.
Population
Where does NaGiNaGI sit among Rust servers?
In the top 36% of all ranked servers, NaGiNaGI sits at #8,005 for player hours over the last seven days.
Is NaGiNaGI a busy server?
Right now, 0 players are on NaGiNaGI, which has 50 slots. Averaging 0 players over seven days, it peaked at 2. The busiest time in the last 48 hours was 10:00 UTC, with an average of 0 players.
Tags and filters
How should you read the tags on NaGiNaGI?
You'll see NaGiNaGI tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^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. 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.
Where does NaGiNaGI appear in the Rust Server Score lists and filters?
Rust Server Score lists that include NaGiNaGI: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
What settings and rules apply on NaGiNaGI?
You will find no gather rate in the name of NaGiNaGI. 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
NaGiNaGI runs which map?
The game generates the procedural map on NaGiNaGI at size 2,517 with seed 481981. 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 NaGiNaGI?
To connect, start Rust, press F1, and type client.connect 64.31.11.27:28080. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 steady term. Strongest in performance (A+); population is the one to work on (F).