Statistical profileOffline
WriteQueueDiagTest
136.169.236.132:28015 checked 5d ago
Connect to this server
1. Main points
Players now
0/ 10
0% full
7-day average
0
peak –
Rank
#15,335
top 69%
Last wipe
6d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 10 slots.
- It ranks #15,335 of all ranked servers, the top 69%, on player hours over the last seven days.
- Its current map went up 6d ago.
2. Players
Figure 1: Players on WriteQueueDiagTest
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of WriteQueueDiagTest
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of WriteQueueDiagTest
What the server publishes and what was recorded
| Address | 136.169.236.132:28015 |
|---|---|
| Region | – |
| Max players | 10 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 23 Oct 2026, 14:46 UTC |
| Hostname | – |
| First seen | 23 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 149 on average | 172 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 133 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 78 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 48 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 242 / 700 |
10. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on WriteQueueDiagTest?
Too few wipes of WriteQueueDiagTest are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 6 days ago.
About the server
Is WriteQueueDiagTest up, and how well has it held up?
Last seen 5 days 22 hours ago, WriteQueueDiagTest is offline in this release. A total of 0 of 120 hours were up over 5 full days, which is 0% of the time. The first sighting of it by Rust Census was on 23 October 2026.
In which location is WriteQueueDiagTest based?
A region is not published by WriteQueueDiagTest. Rust Census does not look up where the machine stands; it shows where a server says it is. 136.169.236.132:28015 is its address.
What version of Rust has been recorded on WriteQueueDiagTest?
This release lists WriteQueueDiagTest on Rust network protocol 2635 and build 168909, running on Windows. Steam updates your game for you, but it has to be on the same protocol to join.
Population
What population has been recorded on WriteQueueDiagTest?
WriteQueueDiagTest is offline at present; its last recording was 5 days 22 hours ago. Averaged across seven days, the count is 0 players.
How does WriteQueueDiagTest compare with other servers in the rankings?
For seven-day player hours, WriteQueueDiagTest is ranked #15,335, placing it in the top 69% of all ranked servers.
Tags, lists
Where does WriteQueueDiagTest appear among the Rust Census lists and filters?
The Rust Census lists that WriteQueueDiagTest fits are: Modded Rust servers, counted. Under these filters it comes 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.
Which meanings do the tags on WriteQueueDiagTest carry?
Read by the game's server browser, WriteQueueDiagTest publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): The server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Rules, map
Which map has been recorded for WriteQueueDiagTest?
The game generates the procedural map on WriteQueueDiagTest.
What settings and rules have been listed for WriteQueueDiagTest?
No gather rate is recorded for WriteQueueDiagTest in its name. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Modded is its section in the server browser, because plugins or settings change the game. The plugin count is Oxide. The server runs VAC, Valve's anti-cheat.
Join details
What is the way to join WriteQueueDiagTest?
You can open the console in Rust with F1 and enter client.connect 136.169.236.132:28015; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp10 | Max players 10 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.