WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 6d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What is the wipe schedule on WriteQueueDiagTest?
WriteQueueDiagTest has too few wipes on record yet for its rhythm to show. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. The world in play now was made 6 days 8 hours ago.
Population
How busy is WriteQueueDiagTest?
Last seen 6 days 7 hours ago, WriteQueueDiagTest is offline at the moment. Averaged over the past week: 0 players.
How does WriteQueueDiagTest rank against other Rust servers?
The top 69% of ranked servers includes WriteQueueDiagTest, at #15,276 for player hours over the last seven days.
Rules and settings
Which map does WriteQueueDiagTest run?
A procedural map, generated by the game, runs on WriteQueueDiagTest.
What are the rules and settings on WriteQueueDiagTest?
No gather rate appears in the name WriteQueueDiagTest. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. The server browser lists it as Modded: plugins or settings change the game. Plugin count: Oxide. Anti-cheat: Valve's VAC is on.
About the server
Which version of Rust does WriteQueueDiagTest run?
Rust network protocol 2635 and build 168909 is the build WriteQueueDiagTest runs, on Windows. To join, your game must match the protocol; Steam handles the update.
Is WriteQueueDiagTest online, and how reliable is it?
Last seen 6 days 7 hours ago, WriteQueueDiagTest is offline right now. 0 of 120 hours up over the last 5 full days, which is 0%. It first appears in Rust Heatmap records on 23 October 2026.
Where is WriteQueueDiagTest located?
A region is not published for WriteQueueDiagTest. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. To connect, use 136.169.236.132:28015.
Tags
Which Rust Heatmap lists and filters include WriteQueueDiagTest?
These Rust Heatmap lists include WriteQueueDiagTest: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
What do the server tags on WriteQueueDiagTest mean?
gmrust (Game mode): Rust survival, standard rules; mp10 (Max players): Slot count: 10; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): To join, run the same version: game protocol 2635; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded are the tags WriteQueueDiagTest publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join WriteQueueDiagTest?
Press F1 in Rust to open the console, then enter client.connect 136.169.236.132:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.