Off air · chart position #15,338
WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 5d ago
Players
WriteQueueDiagTest
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.
Similar servers
Quick answers
About the server
Is WriteQueueDiagTest online, and how reliable is it?
You will not get on WriteQueueDiagTest just now: it is offline, last seen 5 days 16 hours ago. Of the past 5 full days it was running for 0 of 120 hours, or 0% of the time. Rust Charts has tracked it since 23 October 2026.
Where is WriteQueueDiagTest located?
There's no region listed for WriteQueueDiagTest. Where a server says it is — that's what Rust Charts shows, without checking the machine's real location. Connect at 136.169.236.132:28015.
Which version of Rust does WriteQueueDiagTest run?
Rust network protocol 2635 and build 168909 on Windows is the version WriteQueueDiagTest runs. Your game must match the protocol to get in, and Steam keeps it updated for you.
Player counts
How busy is WriteQueueDiagTest?
WriteQueueDiagTest is offline at the moment; the last sighting was 5 days 16 hours ago. Its average over the past week comes to 0 players.
How does WriteQueueDiagTest rank against other Rust servers?
The top 69% of ranked servers includes WriteQueueDiagTest, at #15,338 on player hours for the last week.
Wipes and resets
What is the wipe schedule on WriteQueueDiagTest?
Too few wipes on record for WriteQueueDiagTest to show its rhythm. Thursday 5 November at 19:00 UTC brings the next monthly force wipe, which reaches every Rust server. 5 days 18 hours is how long ago its current world was made.
How it is set up
What are the rules and settings on WriteQueueDiagTest?
No gather rate appears in the name WriteQueueDiagTest. 8 players is the group limit, the default for the game. survival is the game mode, raid, build and gather: the standard game. Fighting and raiding between players is allowed. Modded in the server browser is where it sits; plugins or settings alter the game. The plugins it runs number Oxide. The anti-cheat VAC from Valve is on.
Which map does WriteQueueDiagTest run?
Generated by the game, the map on WriteQueueDiagTest is procedural.
Lists and filters
Which Rust Charts lists and filters include WriteQueueDiagTest?
These Rust Charts lists include WriteQueueDiagTest: Modded Rust servers. These filters on the server list bring it up: 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?
These are the tags WriteQueueDiagTest makes public, and the server browser reads them: gmrust (Game mode): Survival, in the standard Rust form; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team, as the game ships it; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network, as standard for the game; $r? (Region code): This server has no region code; ^o (Oxide): The plugin framework is Oxide, also known as uMod; ^z (Modded): Plugins or changed settings put this server under Modded. Player numbers now, queue size and world creation time sit in the tags as well, shown at the top of this page.
How to join
How do I join WriteQueueDiagTest?
Enter client.connect 136.169.236.132:28015 in the console, which F1 opens once Rust is running. Launch Rust and join on this page is the other way: Rust opens through Steam and connects you.