StatusLive Servers online11,701 Players54,561 Populated3,263 Wiped · 3 h144 Interval5 min Date29 OCT 2026

DWG RG-S5501Server sheetchecked 12m ago

THREE | NITECORE PvE

Online NA 66.51.96.60:28005 checked 12m ago

monthly wipes moddedoxidepve
Connect
Players now 0/ 50 0% 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
Fig. 1

Players

AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Fig. 1Players on THREE | NITECORE PvE
Fig. 2

Server performance

02040608011:0020:0005:0013:0023:0008:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep27 Sep1 Oct25 Oct29 Oct

Top 25% of all ranked servers, top 49% in NA. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

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

  1. 7d 8hThu 5 Nov, 19:00 UTCFW
  2. 35d 8hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 50 on average
32 / 200
02
[US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 38 on average
22 / 200
03
Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average
14 / 100
04
Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | JetNA · no group limit · 1x · monthly · 34 on average
58 / 100
05
[US] Salty Zombies PvE #1 | Skills | Raid | Quests | Jetpack | NA · groups of 20+ · monthly · 24 on average
2 / 150
06
US | For all Mankind PVE | No Raiding/Killing/StealingNA · groups of 8+ · monthly · 12 on average
6 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

Is THREE | NITECORE PvE online, and what uptime has been recorded?

Right now, THREE | NITECORE PvE is recorded as online. Counted from its reported uptime, the last restart was about 3 days 8 hours ago. For the last 7 full days the record is 95 of 168 hours up, 57% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

How does THREE | NITECORE PvE perform, as measured?

The last 48 hours give an average of 17 server fps and a floor of 5. Counted at its highest: 68,166 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,103 MB. Players feel low fps and a climbing entity count as lag.

What location is recorded for THREE | NITECORE PvE?

The NA tag is how THREE | NITECORE PvE lists itself in North America. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 66.51.96.60:28005.

What Rust version is recorded for THREE | NITECORE PvE?

Rust network protocol 2635 and build 168909 on Linux: that is what THREE | NITECORE PvE runs. Steam updates your game, which must be on the same protocol for you to join.

Counts

What player count is recorded on THREE | NITECORE PvE?

0 of 50 slots on THREE | NITECORE PvE are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 1. Over the last 48 hours the busiest hour was 21:00 UTC, at an average of 1 players.

In the rankings, which position does THREE | NITECORE PvE hold?

THREE | NITECORE PvE also measures #919 in North America on the same seven-day player-hour count, at #5,501 globally and in the top 25% of ranked servers.

Wipe data

What is recorded on THREE | NITECORE PvE on wipe day?

An average of 1 players was recorded at the busiest point of its recent wipes. At 2 hours after the latest wipe the crowd was at its peak.

On THREE | NITECORE PvE, when do wipes occur?

The force wipe is the only wipe at THREE | NITECORE PvE, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 4 days 8 hours ago the current world was made. A wipe every month is the schedule its tags set out.

Rules and settings

Which rules and settings are recorded for THREE | NITECORE PvE?

The name of THREE | NITECORE PvE records no gather rate. The group limit is 8 players, the game's default. pve, no fighting other players, is the game mode. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is THREE | NITECORE PvE played?

Size 3,500 with seed 724241993: that is the procedural map THREE | NITECORE PvE runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Lists and filters

On Rust Graphs, which lists and filters contain THREE | NITECORE PvE?

These Rust Graphs lists include THREE | NITECORE PvE: Modded Rust servers, PvE Rust servers, plotted and Rust server list: North America. It is returned by these filters 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.

Which meaning is attached to each tag on THREE | NITECORE PvE?

Tags published by THREE | NITECORE PvE, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp50 (Max players): 50 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^p (PvE): No player combat: the threat comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; NA (North America): In the server browser it appears under North America. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Joining the server

What is the way to connect to THREE | NITECORE PvE?

Enter client.connect 66.51.96.60:28005 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^p,^m,NA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust style.
mp50
Max players 50 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^m
Monthly Monthly wipes, on Facepunch's force wipe.

Gameplay

^p
PvE No player combat: the threat comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Region

NA
North America In the server browser it appears under North America.

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.

KeyTag string decoded