WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 6d ago
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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on WriteQueueDiagTest?
You will find no gather rate in the name of WriteQueueDiagTest. 8 players per group is the default limit. The server runs survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. Plugins or settings change the game; it is listed under Modded in the server browser. Oxide plugins are run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on WriteQueueDiagTest?
Generated by the game, the map is procedural on WriteQueueDiagTest.
Tags and filters
Which lists and filters on Rust Server Index is WriteQueueDiagTest filed under?
Filed under these Rust Server Index lists is WriteQueueDiagTest: Modded Rust servers, filed by play style. 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.
Which tags are attached to WriteQueueDiagTest, and what do they stand for?
The server's own tags are listed here, and the game's server browser reads them: WriteQueueDiagTest gives gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): Player cap: 10; ts8 (Group limit): The team limit is 8, as in the standard game; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): The game build here is 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): The region code field is left empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe schedule
Which wipe timetable does WriteQueueDiagTest follow?
Its rhythm is not yet clear, since the record holds too few of WriteQueueDiagTest's wipes. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 6 days 13 hours.
Population
How is WriteQueueDiagTest ranked compared with the rest?
On player hours over seven days, WriteQueueDiagTest takes #15,270, within the top 69% of ranked servers.
What does the player count on WriteQueueDiagTest look like?
At present WriteQueueDiagTest is offline; its last sighting was 6 days 12 hours ago. Filed under seven-day average: 0 players.
Server facts
What version does WriteQueueDiagTest use?
Rust network protocol 2635 and build 168909 on Windows is what you will find on WriteQueueDiagTest. To join you need the same protocol; Steam handles the update.
What is the uptime and current status of WriteQueueDiagTest?
The server is down at this moment; the last sighting of WriteQueueDiagTest was 6 days 12 hours ago. Uptime for the last 6 full days came to 0%, 0 hours out of 144. It was first recorded by Rust Server Index on 23 October 2026.
What is the location of WriteQueueDiagTest?
There is no region on record for WriteQueueDiagTest; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 136.169.236.132:28015.
Joining the server
What steps lead onto WriteQueueDiagTest?
If you would rather use the console, press F1 in Rust and enter client.connect 136.169.236.132:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp10
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.