Offline 136.169.236.132:28015 checked 6d ago
WriteQueueDiagTest
Connect
srv = rust.server("136.169.236.132:28017")
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 136.169.236.132:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 14:46 UTC
- hostname
- –
- first seen
- 23 Oct 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 · 150 on average | 166/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 81/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 258/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Player counts
What position does WriteQueueDiagTest take in the server rankings?
Rank #15,341 on seven-day player hours for WriteQueueDiagTest, within the top 69% of all ranked servers.
How full does WriteQueueDiagTest run?
Offline now for WriteQueueDiagTest, with the last sample 6 days ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on WriteQueueDiagTest?
The build is Rust network protocol 2635 and build 168909 on Windows, run by WriteQueueDiagTest. The protocol has to match before you can join, and Steam does the updating.
Is WriteQueueDiagTest up, and what does its uptime show?
WriteQueueDiagTest is offline at this refresh; the last response came 6 days ago. Over the last 5 full days the hours up number 0 of 120, 0%. Its earliest recorded date in Rust Data is 23 October 2026.
In which location is WriteQueueDiagTest hosted?
No region is published by WriteQueueDiagTest. 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 136.169.236.132:28015.
Map and rules
What rules and settings are recorded for WriteQueueDiagTest?
No gather rate appears in the name: WriteQueueDiagTest. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on WriteQueueDiagTest?
A procedural map runs on WriteQueueDiagTest, generated by the game.
Wipe data
When does WriteQueueDiagTest wipe, and on what schedule?
A rhythm cannot be read from the wipes of WriteQueueDiagTest on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 6 days 1 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold WriteQueueDiagTest, and which filters?
The Rust Data lists that WriteQueueDiagTest fits are: 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 week.
Which meanings do the tags on WriteQueueDiagTest hold?
These tags are published by WriteQueueDiagTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join WriteQueueDiagTest?
Enter client.connect 136.169.236.132:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.