RUST METRICSFlight deck · live data
Data live Servers11,617 Players34,993 Populated2,836 Fresh wipes 3 h74 Scan5 min
‹ All servers66.51.96.60:28005
Online Full Queue Fresh wipe Wipe due No query

THREE | NITECORE PvE

Online NA 66.51.96.60:28005 checked 9m ago

monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 05:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 5 SERVER FPS

Server fps

48 h low 5 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 66,043 ×1000

Entities

48 h range 65,467–68,166 · memory 2,562 MB
1239 ET SINCE RESTART 3D 05H

Uptime

3 days 5 hours since its last restart, at the last reading
7-day average0peak 1
Rank#5,517top 25% · #917 in NA
Last wipe4d agomonthly schedule
Next wipe7d 12hThu 5 Nov, 19:00 UTC FW
Memory2,562MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608007:0016:0001:0010:0020:0005: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.

REC 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.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 12hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 12hFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on THREE | NITECORE PvE when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe.

How often does THREE | NITECORE PvE wipe, and when?

The only wipe for THREE | NITECORE PvE is the force wipe, once a month. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 4 days 5 hours ago the current world was made. Its tags carry a monthly wipe schedule.

Tags

Which tags does THREE | NITECORE PvE carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): The server browser files it under North America from THREE | NITECORE PvE. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show THREE | NITECORE PvE?

On Rust Metrics, THREE | NITECORE PvE sits in these lists: Modded Rust servers, checked live, Rust PvE servers and North America: server readout. Reading: server list filters. It comes up under 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.

Player count

What position does THREE | NITECORE PvE hold among Rust servers?

Ranked by seven-day player hours, THREE | NITECORE PvE sits at #5,517 and #917 in North America, inside the top 25%.

What is the population on THREE | NITECORE PvE?

Current headcount on THREE | NITECORE PvE: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 21:00 UTC over the last 48 hours.

Server

Where does THREE | NITECORE PvE sit?

Its NA tag places THREE | NITECORE PvE in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 66.51.96.60:28005.

What Rust version is THREE | NITECORE PvE on?

Reading: THREE | NITECORE PvE, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for THREE | NITECORE PvE?

Reading: 17 server fps on average across the last 48 hours. It never dropped below 5. Check: entities. The peak was 68,166, counting buildings, deployables and the rest of the world. Memory peak: 3,103 MB. What players call lag comes from low fps and an entity count on the rise.

Is THREE | NITECORE PvE up, and how often does it stay up?

Check: connection. THREE | NITECORE PvE is online at this moment. By its reported uptime, the last restart was roughly 3 days 5 hours ago. Reading: 57% uptime over the last 7 full days. It was up 95 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is THREE | NITECORE PvE configured, and what rules are in force?

Reading the name gives no gather rate for THREE | NITECORE PvE. 8 players per group, the default value. pve, other players are not fought — that is the game mode. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is THREE | NITECORE PvE on?

From seed 724241993, the game generates the procedural map on THREE | NITECORE PvE. Its size is 3,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to THREE | NITECORE PvE?

Press F1 in Rust and enter client.connect 66.51.96.60:28005. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

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, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Region

NA
North America The server browser files it 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.