Offline 135.148.15.16:26681 checked 12d ago
zquos test
Connect
srv = rust.server("135.148.15.16:26682")
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 22 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 17:26 UTC12d ago | 0 | NaN | running | 0 |
| 1 | Tue 22 Sep, 01:02 UTC37d ago | 1 | halved by day 1 | 24.7 days | 1 |
# 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
3000 · seed 50000
- map
- Procedural Map
- size
- 3000
- seed
- 50000
Server
srv.info()- address
- 135.148.15.16:26681
- region
- –
- max players
- 75
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 17:26 UTC
- hostname
- –
- first seen
- 22 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 · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 168/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 100/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 248/700 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does zquos test rank?
Player hours over seven days put zquos test at #15,202, in the top 70% of the ranked set.
How full does zquos test run?
Offline now for zquos test, with the last sample 12 days 11 hours ago.
Server facts
Which Rust version is zquos test on?
Rust network protocol 2634 and build 167781 on Linux is what zquos test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is zquos test, and is it online now?
Offline now for zquos test, last seen 12 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 22 September 2026.
Where does zquos test sit?
For zquos test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 135.148.15.16:26681 is its address.
Settings and map
What rules and settings are recorded for zquos test?
The name zquos test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has zquos test loaded?
The game generates the map on zquos test: procedural, size 3,000, seed 50000. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does zquos test wipe, and on what schedule?
Too few wipes are on record for zquos test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 12 days 21 hours ago.
On zquos test, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 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.
Lists and tags
Which lists on Rust Data hold zquos test, and which filters?
On Rust Data, zquos test 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; Last wipe: In the last 2 weeks.
Which meanings do the tags on zquos test hold?
These tags are published by zquos test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
What is the way to join zquos test?
In Rust, F1 opens the console: type client.connect 135.148.15.16:26681. Launch Rust on this page does the same by opening the game through Steam and connecting.