RUST METRICSFlight deck · live data
Data live Servers11,773 Players67,310 Populated3,523 Fresh wipes 3 h192 Scan5 min
‹ All servers184.4.38.100:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Development Server

Offline 184.4.38.100:28015 checked 28d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

10% 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#14,314top 60%
Last wipe28d agono schedule published
Next wipe–no wipe 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
15k10k15k20k1 Oct2 Oct3 Oct5 Oct6 Oct7 Oct

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

PLAN

Wipe schedule

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

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

How often does Test Development Server wipe, and when?

To tell the rhythm of Test Development Server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 28 days 12 hours ago.

Tags

Which tags does Test Development Server carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166440 (Build): Game build reading: 166440; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Test Development Server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Test Development Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Test Development Server: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Test Development Server hold among Rust servers?

Ranking for Test Development Server: #14,314 on seven-day player hours, top 60% of all ranked servers.

How full does Test Development Server get?

Reading for Test Development Server: offline at this moment; last seen 28 days 12 hours ago.

Server

Which location does Test Development Server run from?

No region comes from Test Development Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 184.4.38.100:28015.

What Rust version is Test Development Server on?

Rust network protocol 2634 and build 166440 on Windows is the build Test Development Server runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Test Development Server, and is it online now?

Test Development Server reports offline. The last reading came 28 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Test Development Server enforce, and what are its settings?

Reading the name gives no gather rate for Test Development Server. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Test Development Server on?

Check: map. Procedural, generated by the game, on Test Development Server.

Connection

How do you connect to Test Development Server?

To join: start Rust, press F1 and type client.connect 184.4.38.100:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166440,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166440
Build Game build reading: 166440.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.