RUST METRICSFlight deck · live data
Data live Servers11,595 Players33,948 Populated2,868 Fresh wipes 3 h70 Scan5 min
‹ All servers76.131.4.215:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Dev Testing

Offline 76.131.4.215:28015 checked 6d 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 avg7-day peak
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 average1peak 1
Rank#12,959top 58%
Last wipe15d 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
15k10k15k20k13 Oct16 Oct19 Oct22 Oct25 Oct28 Oct

Top 58% 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 Rust Dev Testing wipe, and when?

To tell the rhythm of Rust Dev Testing, 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 15 days 2 hours ago.

Tag meanings

How should you read the tags on Rust Dev Testing?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Game build reading: 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Rust Dev Testing. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Rust Dev Testing?

These Rust Metrics lists carry Rust Dev Testing: 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 Rust Dev Testing sit in the rankings?

Ranking for Rust Dev Testing: #12,959 on seven-day player hours, top 58% of all ranked servers.

How full does Rust Dev Testing get?

Rust Dev Testing is not responding; status offline, last seen 6 days 8 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Operator and location

Where does Rust Dev Testing sit?

No region comes from Rust Dev Testing. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 76.131.4.215:28015.

What Rust version is Rust Dev Testing on?

Rust network protocol 2634 and build 167584 on Windows is the build Rust Dev Testing runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Rust Dev Testing, and is it online now?

Reading: offline. Rust Dev Testing last answered 6 days 8 hours ago. Reading: 1% uptime over the last 7 full days. It was up 2 of 168 hours. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Map and rules

What rules does Rust Dev Testing enforce, and what are its settings?

Check: gather rate. The name Rust Dev Testing does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Rust Dev Testing?

Procedural map on Rust Dev Testing, made by the game's generator.

Join

How do you connect to Rust Dev Testing?

Press F1 in Rust and enter client.connect 76.131.4.215:28015. 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?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Game build reading: 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.