WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 5d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestTop 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
newest first| 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- 186/500
- 134/100
- 179/225
- 91/700
- 284/200
- 236/700
Quick answers
from the figures on this pageReset cycle
What wipe timing does WriteQueueDiagTest follow?
The rhythm of WriteQueueDiagTest's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 6 days ago.
Tags
How should you read the tags on WriteQueueDiagTest?
Tags published by WriteQueueDiagTest, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does WriteQueueDiagTest appear in Rust Metrics lists and filters?
These Rust Metrics lists carry WriteQueueDiagTest: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Occupancy
What position does WriteQueueDiagTest hold among Rust servers?
Ranking for WriteQueueDiagTest: #15,344 on seven-day player hours, top 69% of all ranked servers.
What player count does WriteQueueDiagTest carry?
Status for WriteQueueDiagTest: offline. Last seen 5 days 23 hours ago. Seven-day reading: 0 players on average.
Operator and location
Where does WriteQueueDiagTest sit?
No region comes from WriteQueueDiagTest. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 136.169.236.132:28015.
What Rust version is WriteQueueDiagTest on?
Rust network protocol 2635 and build 168909 on Windows is the build WriteQueueDiagTest runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is WriteQueueDiagTest, and is it online now?
WriteQueueDiagTest reports offline. The last reading came 5 days 23 hours ago. Uptime for the last 5 full days: 0 of 120 hours, or 0%. The first sighting on Rust Metrics was 23 October 2026.
Rules and settings
How is WriteQueueDiagTest configured, and what rules are in force?
No gather rate appears in the name: WriteQueueDiagTest. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on WriteQueueDiagTest?
The game generates a procedural map for WriteQueueDiagTest.
How to join
How do you connect to WriteQueueDiagTest?
Press F1 in Rust and enter client.connect 136.169.236.132:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.