RUST METRICSFlight deck · live data
Data live Servers11,824 Players75,694 Populated3,728 Fresh wipes 3 h230 Scan5 min
‹ All servers185.207.139.24:28018
Offline Full Queue Fresh wipe Wipe due No query

DOOR_TEST

Offline 185.207.139.24:28018 checked 43d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,419no region published
Last wipe43d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep
PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 15 Sep, 18:05 UTC43d ago 0 – running 0

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on DOOR_TEST?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does DOOR_TEST wipe, and when?

The rhythm of DOOR_TEST's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 days 18 hours ago the current world was made.

Lists and filters

Which tags does DOOR_TEST carry, and what do they mean?

Tags published by DOOR_TEST, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does DOOR_TEST appear in Rust Metrics lists and filters?

Rust Metrics lists featuring DOOR_TEST: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does DOOR_TEST sit in the rankings?

Ranking for DOOR_TEST: #15,419 on seven-day player hours, top – of all ranked servers.

What player count does DOOR_TEST carry?

Status for DOOR_TEST: offline. Last seen 43 days 18 hours ago.

Server

What location is DOOR_TEST hosted in?

No region tag on DOOR_TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.207.139.24:28018.

What Rust version is DOOR_TEST on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by DOOR_TEST. To get in, your game needs the same protocol; Steam applies the update.

Is DOOR_TEST up, and how often does it stay up?

DOOR_TEST reports offline. The last reading came 43 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Map and rules

What rules does DOOR_TEST enforce, and what are its settings?

Reading the name gives no gather rate for DOOR_TEST. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Connection

What do you do to join DOOR_TEST?

Press F1 in Rust and enter client.connect 185.207.139.24:28018. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.