Local forecast
WriteQueueDiagTest
Offline 136.169.236.132:28015 checked 5d ago
Current conditions
observed 5d agoplayers now
0% full
- 7-day average
- 0
- peak –
- Rank
- #15,344
- top 69%
- Last wipe
- 5d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
Next wipe
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
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.
Past weather: its 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
How reliable is WriteQueueDiagTest, and is it online now?
Last seen 5 days 7 hours ago, WriteQueueDiagTest is offline now. In the last 4 full days it stayed up 0 of 96 hours, 0% of the time. It came to Rust Wipe Stats's notice first on 23 October 2026.
What location is WriteQueueDiagTest based in?
There is no published region for WriteQueueDiagTest. Rust Wipe Stats does not look up where the machine stands; it shows where the server says it is. You can reach it at 136.169.236.132:28015.
What Rust version is WriteQueueDiagTest on?
On WriteQueueDiagTest you will find Rust network protocol 2635 and build 168909, hosted on Windows. To join you need the same protocol, and Steam handles the update.
Server tags
What do WriteQueueDiagTest's tags tell you?
These are the tags WriteQueueDiagTest publishes for the game's server browser to read: gmrust (Game mode): Standard survival, the Rust way; mp10 (Max players): It holds 10 players; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): It runs game build 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region field is left blank; ^o (Oxide): The plugins run through Oxide (uMod); ^z (Modded): Modded is its category, with plugins or settings changing the game. The tags also carry the current players, the queue and when the world was created; you will find them at the top of this page.
Which Rust Wipe Stats filters and lists carry WriteQueueDiagTest?
WriteQueueDiagTest appears in the following Rust Wipe Stats lists: Modded Rust servers. Find it on the server list under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Settings and rules
Which map is in use on WriteQueueDiagTest?
The game generates the map on WriteQueueDiagTest, a procedural one.
What settings does WriteQueueDiagTest use, and what rules does it enforce?
Gather rate is not given in the name for WriteQueueDiagTest. Groups fall back to the game's default of 8 players. survival is the game mode, the usual game of gathering, building and raiding. You can fight other players and raid their bases. Plugins or settings change the game here, and the browser files it under Modded. Oxide are the plugin frameworks it runs. Valve anti-cheat (VAC) runs on this server.
Wipe times
On what schedule does WriteQueueDiagTest wipe?
The record of WriteQueueDiagTest's wipes is too thin yet to show its rhythm. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. The world it is running now dates from 5 days 9 hours.
Population
How many players does WriteQueueDiagTest hold?
At this moment WriteQueueDiagTest is down, having last been seen 5 days 7 hours ago. The seven-day average stands at 0 players.
What position does WriteQueueDiagTest hold among Rust servers?
The last seven days of player hours rank WriteQueueDiagTest at #15,344, in the top 69% of ranked servers.
Getting in
What steps let you join WriteQueueDiagTest?
Enter client.connect 136.169.236.132:28015 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you.