Rust Data LabData lab · live
Live readings Servers11,715 Players57,218 Populated3,311 Fresh wipes · 3h174 Sampled every 5 min

Element card · group Modded · atomic number 15,338, its rank

WriteQueueDiagTest

Offline 136.169.236.132:28015 checked 5d ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 10 0% full Room to join
7-day average0peak –
Rank · atomic number#15,338top 69%
Last wipe5d agono schedule published
Next wipe–no wipe seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
  1. 1 Sh ShockRust | Bl… 143
    ShockRust | Blue | NoLimit no group limit · 149 on average 143/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 135
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 135/ 100
  3. 3 Re RETRO RUST #1 … 188
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 188/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 77
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 77/ 700
  5. 5 Ru RustSpain.com … 9
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 9/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 19
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 19/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on WriteQueueDiagTest?

The map on WriteQueueDiagTest is procedural, made by the game.

What settings and rules apply on WriteQueueDiagTest?

No gather rate appears in the name of WriteQueueDiagTest. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. In the server browser it sits under Modded: the game is changed by plugins or settings. Plugins in use: Oxide. The VAC anti-cheat from Valve is enabled.

Server facts

Which location is WriteQueueDiagTest based in?

Nothing about a region is published by WriteQueueDiagTest. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 136.169.236.132:28015.

Which Rust version is WriteQueueDiagTest on?

Rust network protocol 2635 and build 168909 on Windows is what WriteQueueDiagTest uses. Joining requires the same protocol on your game; Steam takes care of updating it.

Does WriteQueueDiagTest stay up, and how reliable is its uptime?

WriteQueueDiagTest is not online at the moment; the last sighting was 5 days 18 hours ago. For the last 5 full days, 0 of 120 hours were online, giving 0% uptime. It first appeared to Rust Data Lab on 23 October 2026.

Wipe schedule

When does WriteQueueDiagTest wipe, and how often?

Too few wipes are on record for WriteQueueDiagTest to reveal a rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 5 days 19 hours ago the current world was made.

Where it appears

What should you understand from the tags WriteQueueDiagTest carries?

The game's server browser reads the tags WriteQueueDiagTest publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Player slots: 10; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): A region code has not been set here; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): Plugins or settings alter the game, so it lists under Modded. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does WriteQueueDiagTest come up?

You will find WriteQueueDiagTest on the following Rust Data Lab lists: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Player numbers

How does WriteQueueDiagTest compare with other servers in the rankings?

Player hours over the last week put WriteQueueDiagTest at #15,338, inside the top 69% of ranked servers.

How full is WriteQueueDiagTest right now?

No live signal from WriteQueueDiagTest right now, which was last seen 5 days 18 hours ago. The past week gives an average of 0 players.

Connection

How can you connect to WriteQueueDiagTest?

Open the console with F1 in Rust and type client.connect 136.169.236.132:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp10
Max players Player slots: 10.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code A region code has not been set here.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.