WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 6d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Quick answers
Population
How does WriteQueueDiagTest rank against other Rust servers?
The last seven days of player hours place WriteQueueDiagTest at #15,310, within the top 69% of all ranked servers.
How busy is WriteQueueDiagTest?
WriteQueueDiagTest is offline at this count; we last saw it 6 days 2 hours ago. Counted over seven days: an average of 0 players.
Lists and tags
What do the server tags on WriteQueueDiagTest mean?
These are the tags WriteQueueDiagTest publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): You can join up to 10 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code is left blank; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): This server appears under Modded because plugins or settings alter the game. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include WriteQueueDiagTest?
WriteQueueDiagTest appears among the Rust Population lists that follow: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Wipe schedule
What is the wipe schedule on WriteQueueDiagTest?
Too few wipes are on record for WriteQueueDiagTest to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 6 days 3 hours ago.
Settings
Which map does WriteQueueDiagTest run?
The map on WriteQueueDiagTest is procedural, made by the game.
What are the rules and settings on WriteQueueDiagTest?
Nothing in WriteQueueDiagTest's name says how gather works. No limit is set beyond the standard 8 players per group. This server runs survival, raid, build and gather: the standard game. Fighting and raiding between players is allowed. Modded is its browser category: plugins or settings change the game. The plugins it runs are Oxide. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does WriteQueueDiagTest run?
Rust network protocol 2635 and build 168909 on Windows is what WriteQueueDiagTest uses. The protocol must match for you to join, and Steam updates it for you.
Is WriteQueueDiagTest online, and how reliable is it?
Currently offline, WriteQueueDiagTest was last seen 6 days 2 hours ago. Over the last 5 full days, 0 of 120 hours were online, or 0%. On 23 October 2026, Rust Population saw it for the first time.
Where is WriteQueueDiagTest located?
A region is not published by WriteQueueDiagTest. The location a server claims is what Rust Population shows, not the place where the machine stands. Connect at 136.169.236.132:28015.
Getting in
How do I join WriteQueueDiagTest?
To connect directly, open Rust's console with F1 and type client.connect 136.169.236.132:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.