Online 168.100.161.9:28049 checked 3h ago
Zautaz Private PVE test server
Connect
srv = rust.server("168.100.161.9:28046")
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, 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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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 10 Oct, 10:50 UTC18d ago | 1 | NaN | running | 0 |
| 1 | Fri 2 Oct, 18:56 UTC26d ago | 1 | halved by day 1 | 7.7 days | 0 |
| 2 | Tue 22 Sep, 18:58 UTC36d ago | 1 | halved by day 1 | 10 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
3750 · seed 426539
- map
- Procedural Map
- size
- 3750
- seed
- 426539
Server
srv.info()- address
- 168.100.161.9:28049
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 10:50 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
How does Zautaz Private PVE test server compare in the rankings?
Player hours over seven days put Zautaz Private PVE test server at #15,323, in the top 69% of the ranked set.
What population does Zautaz Private PVE test server carry?
Current row: 0 players on Zautaz Private PVE test server, against 100 slots. Over the last seven days it averaged 0 players.
Server facts
How smoothly does Zautaz Private PVE test server run?
Averaged over 48 hours: 5 server fps, never under 5. The entity count peaked at 82,253, covering buildings, deployables and the rest of the world. The memory field tops out at 2,142 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Zautaz Private PVE test server on?
Rust network protocol 2635 and build 168909 on Linux is what Zautaz Private PVE test server runs. The protocol has to match before you can join, and Steam does the updating.
Is Zautaz Private PVE test server up, and what does its uptime show?
Online is the state at the latest refresh for Zautaz Private PVE test server. The uptime it reports puts the last restart about 16 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does Zautaz Private PVE test server sit?
No region is published by Zautaz Private PVE test server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 168.100.161.9:28049 is its address.
Settings and map
Which rules apply on Zautaz Private PVE test server, and what settings?
The name Zautaz Private PVE test server carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Zautaz Private PVE test server selected?
The game generates the map on Zautaz Private PVE test server: procedural, size 3,750, seed 426539. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does Zautaz Private PVE test server wipe, and how often?
Zautaz Private PVE test server wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 18 days 9 hours ago, and that is the one in play.
On Zautaz Private PVE test server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Tags, lists
Where does Zautaz Private PVE test server appear among Rust Data lists and filters?
On Rust Data, Zautaz Private PVE test server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Zautaz Private PVE test server hold?
Read by the game's server browser, the tags Zautaz Private PVE test server publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into Zautaz Private PVE test server?
In Rust, F1 opens the console: type client.connect 168.100.161.9:28049. Launch Rust on this page does the same by opening the game through Steam and connecting.