Offline 67.222.101.139:29015 checked 39d ago
PRIVATE
Connect
srv = rust.server("67.222.101.139:29401")
print(srv.connect_command)Right now
srv.summary()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. 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 bestWipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 19 Sep, 12:24 UTC40d ago | 1 | NaN | running | 1 |
| 1 | Fri 18 Sep, 23:16 UTC40d ago | 1 | NaN | 0.5 days | 0 |
| 2 | Fri 18 Sep, 12:41 UTC41d ago | 1 | NaN | 0.4 days | 0 |
| 3 | Wed 16 Sep, 12:20 UTC43d ago | 1 | held half | 2 days | 0 |
| 4 | Tue 15 Sep, 10:52 UTC44d ago | 1 | NaN | 1.1 days | 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 67.222.101.139:29015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Sep 2026, 12:24 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 144/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 196/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 90/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 226/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
What position does PRIVATE take in the server rankings?
Over the last seven days PRIVATE sits at #15,427 on player hours, in the top – of ranked servers.
What population does PRIVATE carry?
PRIVATE returns no live count at this refresh, having last been seen 39 days 18 hours ago.
About the server
What is the Rust version on PRIVATE?
The build is Rust network protocol 2633 and build 162929 on Windows, run by PRIVATE. Steam updates your game for you, but the protocol must match to join.
Is PRIVATE up, and what does its uptime show?
Offline now for PRIVATE, last seen 39 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does PRIVATE run from?
No region is published by PRIVATE. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 67.222.101.139:29015 is its address.
Settings and map
Which settings and rules does PRIVATE run?
The name PRIVATE carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does PRIVATE wipe, and how often?
No next wipe can be predicted for PRIVATE, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 40 days 5 hours ago.
What is wipe day on PRIVATE like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Where does PRIVATE appear among Rust Data lists and filters?
The Rust Data lists that PRIVATE fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on PRIVATE?
These tags are published by PRIVATE and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Recorded game build: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join PRIVATE?
Enter client.connect 67.222.101.139:29015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.