On the class lists: C− (57), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#5,501top 25% · #919 in NA
Last wipe4d agomonthly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
75/ 100
B
Holds a respectable place: #5,501 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
28/ 100
F
Needs to work on its frame rate: 17 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 term to build on.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 25% of all ranked servers, top 49% in NA. 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
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 8hThu 5 Nov, 19:00 UTCFW
35d 8hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 23:59 UTC4d ago
1
–
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
You'll see THREE | NITECORE PvE listed in North America, tagged NA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 66.51.96.60:28005.
Is THREE | NITECORE PvE up, and how steady is its uptime?
You can join now: THREE | NITECORE PvE is online. According to its reported uptime, the last restart was about 3 days 9 hours ago. It was up 95 of 168 hours over the last 7 full days, which is 57% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does THREE | NITECORE PvE run?
The average over the last 48 hours was 17 server fps, and it never went below 5. At its peak, it held 68,166 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,103 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is THREE | NITECORE PvE running?
The server THREE | NITECORE PvE is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does THREE | NITECORE PvE wipe its map?
THREE | NITECORE PvE wipes with the force wipe and at no other time. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 4 days 9 hours. Its tags record that it wipes monthly.
What happens on THREE | NITECORE PvE when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 2 hours after it began.
Player numbers
Where does THREE | NITECORE PvE sit among Rust servers?
In North America, THREE | NITECORE PvE is #919, and overall it is #5,501 on player hours over the last seven days, in the top 25% of all ranked servers.
What does the population on THREE | NITECORE PvE look like?
With 50 slots available, THREE | NITECORE PvE currently has 0 players. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 21:00 UTC, with an average of 1 players.
Lists and filters
What do THREE | NITECORE PvE's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): You will find it under North America in the browser are the tags THREE | NITECORE PvE publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does THREE | NITECORE PvE appear in the Rust Server Score lists and filters?
These Rust Server Score lists count THREE | NITECORE PvE among them: Modded Rust servers, graded, Rust PvE servers, graded and North America Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last week.
Rules and settings
What settings and rules apply on THREE | NITECORE PvE?
The name of THREE | NITECORE PvE gives no gather rate. The group limit stays at the game's default of 8 players. You get pve here, no PvP between players. 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.
Can you tell me which map THREE | NITECORE PvE uses?
THREE | NITECORE PvE runs a game-generated procedural map at size 3,500, seed 724241993. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to THREE | NITECORE PvE?
To connect, start Rust, press F1, and type client.connect 66.51.96.60:28005. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^p,^m,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
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 codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).