private do not join!!!
Online NA 66.51.97.67:28050 checked 12m ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers, top 82% in NA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 18h.
The force wipe · high confidenceComing wipes
- 7d 18hThu 5 Nov, 19:00 UTC19:00 UKFW
- 35d 18hThu 3 Dec, 19:00 UTC19:00 UKFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
every wipe as a delivery, newest first-
Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 18hNext wipe expected · the force wipe
-
Thu 1 Oct, 23:41 UTC FW 00:41 UK · 27d agoForce wipe delivered
- Peak
- 0
- Crowd
- –
- Lasted
- running
- Players before
- 0
-
Sun 27 Sep, 22:42 UTC 23:42 UK · 31d agoWipe delivered
- Peak
- 3
- Crowd
- halved by day 1
- Lasted
- 4 days
- Players before
- 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Population
How does private do not join!!! compare with other Rust servers in the rankings?
Ranked #15,349 on player hours over the last seven days, private do not join!!! is #1,521 in North America and in the top 69% of all ranked servers.
Is private do not join!!! busy at the moment?
At the moment 0 players are on private do not join!!!, which has 50 slots. Averaged over the past week: 0 players.
Server rules
On what map does private do not join!!! take place?
Size 4,500 and seed 1 define the procedural map private do not join!!! runs, generated by the game. You can see the map on RustMaps from this page, since one size and seed give one map.
Which settings and rules apply on private do not join!!!?
You will not find a gather rate in the name of private do not join!!!. The group limit is 24 players. It runs survival, gather, build and raid, as the standard game goes. You can raid and fight other players. Because plugins or settings change the game, it is filed under Modded in the server browser. The plugins run on Oxide. The VAC anti-cheat from Valve is enabled.
Operator and location
What is the location of private do not join!!!?
The NA tag is how private do not join!!! lists its location: North America. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 66.51.97.67:28050.
What is the performance like on private do not join!!!?
Averaged over the last 48 hours, server fps was 5, with a low of 5. The world held as many as 122,127 entities: buildings, deployables and the rest. Memory use peaked at 3,252 MB. Lag, to players, means low fps alongside an entity count on the rise.
Is private do not join!!! up, and how good is its uptime?
private do not join!!! is up and online at the moment. Its reported uptime suggests a restart roughly 6 hours ago. It was up 144 of 168 hours over the last 7 full days, 86% of the time. The first sighting of it by Rust Wipe Tracker came on 13 September 2026.
On what Rust version does private do not join!!! operate?
The version on private do not join!!! is Rust network protocol 2635 and build 168909, running on Linux. Steam keeps your game updated; it has to be on the same protocol to join.
Wipe times
How does private do not join!!! handle its wipe days?
At their busiest, its recent wipes drew an average of 2 players. After 0 hours the latest wipe's crowd hit its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 1 it had fallen below half where the crowd did not hold.
When does private do not join!!! wipe? What schedule does it follow?
private do not join!!! wipes with the force wipe and at no other time, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 27 days have passed since this world was made. Its tags carry a monthly wipe schedule.
Tags and listings
Where does private do not join!!! appear in Rust Wipe Tracker lists and filters?
You will find private do not join!!! on the following Rust Wipe Tracker lists: Modded Rust servers and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the tags on private do not join!!!?
Read off the game's server browser, the tags for private do not join!!! are: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): It holds 50 slots; ts24 (Group limit): Teams are limited to 24 players; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^m (Monthly): One wipe a month, alongside the force wipe; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; NA (North America): In the server browser it appears under North America. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.
How to join
What is the process to join private do not join!!!?
Through this page's Launch Rust, Rust opens in Steam and connects you; otherwise open the console with F1 in Rust and enter client.connect 66.51.97.67:28050.
