Offline 14.12.132.162:28015 checked 42d ago
PveThreat-Dev
Connect
srv = rust.server("14.12.132.162:28016")
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
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 14.12.132.162:28015
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Sep 2026, 01:11 UTC
- hostname
- –
- first seen
- 17 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 | 20/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 42/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 7/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 24/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 92/200 |
Quick answers
From the figures on this page.
Player counts
What position does PveThreat-Dev take in the server rankings?
Player hours over seven days put PveThreat-Dev at #14,182, in the top – of the ranked set.
How many players does PveThreat-Dev hold at once?
Offline now for PveThreat-Dev, with the last sample 42 days 22 hours ago.
Server data
Which Rust version is PveThreat-Dev on?
The build is Rust network protocol 2633 and build 163794 on Windows, run by PveThreat-Dev. Joining needs the same protocol on your game; Steam handles the update.
How reliable is PveThreat-Dev, and is it up?
The latest sample has PveThreat-Dev offline, with a last sighting 42 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 17 September 2026.
Which location does PveThreat-Dev run from?
There is no region published for PveThreat-Dev. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 14.12.132.162:28015.
Rules, settings, map
Which rules apply on PveThreat-Dev, and what settings?
You will not find a gather rate in the string PveThreat-Dev. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has PveThreat-Dev selected?
The game generates its map: procedural, on PveThreat-Dev.
Wipe data
When does PveThreat-Dev wipe, and how often?
The record for PveThreat-Dev holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 43 days 2 hours ago.
Tags and filters
Which lists on Rust Data hold PveThreat-Dev, and which filters?
On Rust Data, PveThreat-Dev appears in these lists: 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 PveThreat-Dev?
These tags are published by PveThreat-Dev and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp8 (Max players): Slot count: 8; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Build number: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join PveThreat-Dev?
Enter client.connect 14.12.132.162:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.