Online NA 66.51.96.60:28005 checked 8m ago
THREE | NITECORE PvE
Connect
srv = rust.server("66.51.96.60:28006")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 24% of all ranked servers, top 49% in NA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 19h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 19h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 23:59 UTC4d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3500 · seed 724241993
- map
- Procedural Map
- size
- 3500
- seed
- 724241993
Server
srv.info()- address
- 66.51.96.60:28005
- region
- NA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 25 Oct 2026, 01:18 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No Killing | NA · groups of 8+ · monthly · 48 on average | 51/200 |
| 1 | [US] RustEZ Survival PvE | No Decay | No Raiding | No Killing | NA · groups of 8+ · monthly · 37 on average | 41/200 |
| 2 | Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | Jet | NA · no group limit · 1x · monthly · 37 on average | 103/125 |
| 3 | Zombie Land PVE Monthly | Raids | Skills | Custom Maps | NA · groups of 14+ · monthly · 33 on average | 37/100 |
| 4 | [US] Salty Zombies PvE #1 | Skills | Raid | Quests | Jetpack | | NA · groups of 20+ · monthly · 24 on average | 37/150 |
| 5 | US | For all Mankind PVE | No Raiding/Killing/Stealing | NA · groups of 8+ · monthly · 12 on average | 13/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does THREE | NITECORE PvE rank?
On seven-day player hours THREE | NITECORE PvE is #5,424 overall and #912 in North America, inside the top 24% of all ranked servers.
How full does THREE | NITECORE PvE run?
The sample now reads 1 players for THREE | NITECORE PvE, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 00:00 UTC, mean 1 players.
Server facts
What does performance look like on THREE | NITECORE PvE?
The 48-hour average is 15 server fps, with a low of 5. Entity numbers reached 68,166, and that includes buildings, deployables and the rest. Memory peaked at 3,103 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does THREE | NITECORE PvE run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by THREE | NITECORE PvE. The protocol has to match before you can join, and Steam does the updating.
How reliable is THREE | NITECORE PvE, and is it up?
The current sample puts THREE | NITECORE PvE online. Count back 3 days 22 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 95 of 168, 57%. Rust Data logged it first on 13 September 2026.
Which location does THREE | NITECORE PvE run from?
With its NA tag, THREE | NITECORE PvE lists itself in North America. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 66.51.96.60:28005.
Rules, settings, map
Which rules apply on THREE | NITECORE PvE, and what settings?
The name THREE | NITECORE PvE carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has THREE | NITECORE PvE loaded?
Size 3,500, seed 724241993: the procedural map on THREE | NITECORE PvE, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does THREE | NITECORE PvE wipe, and on what schedule?
A single wipe each month, the force wipe, is all THREE | NITECORE PvE does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 4 days 22 hours ago. Its tags carry a monthly wipe schedule.
What is wipe day on THREE | NITECORE PvE like?
Across recent wipes the busiest point averaged 1 players. 2 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain THREE | NITECORE PvE?
The Rust Data lists that THREE | NITECORE PvE fits are: Modded Rust servers, Rust PvE servers and North America Rust servers. It appears under 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.
How should you read the server tags on THREE | NITECORE PvE?
These tags are published by THREE | NITECORE PvE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): North America is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join THREE | NITECORE PvE?
In Rust, F1 opens the console: type client.connect 66.51.96.60:28005. Launch Rust on this page does the same by opening the game through Steam and connecting.