RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h113 Scan5 min
‹ All servers31.36.131.153:28015
Offline Full Queue Fresh wipe Wipe due No query

destiny local test

Offline 31.36.131.153:28015 checked 25d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 4 6 8 PAX 1 /8

Players now

12% 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#13,832top 61%
Last wipe26d 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
15k10k15k20k25 Sep28 Sep1 Oct3 Oct6 Oct9 Oct

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

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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 15:29 UTC26d ago 1 – 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

Wipe timing

What should you expect from wipe day on destiny local test?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does destiny local test wipe, and when?

The rhythm of destiny local 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. 26 days 2 hours ago the current world was made.

Lists and filters

Which tags does destiny local test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp8 (Max players): Slots: 8; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from destiny local test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does destiny local test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry destiny local test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does destiny local test hold among Rust servers?

Player hours over seven days put destiny local test at #13,832, in the top 61% of all ranked servers.

What player count does destiny local test carry?

destiny local test is not responding; status offline, last seen 25 days 21 hours ago.

Operator and location

Which location does destiny local test run from?

No region comes from destiny local test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.36.131.153:28015.

What Rust version is destiny local test on?

Rust network protocol 2634 and build 166586 on Windows is the build destiny local test runs. Matching protocol is required to join. Let Steam update your game.

Is destiny local test up, and how often does it stay up?

destiny local test reports offline. The last reading came 25 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Map and rules

What rules does destiny local test enforce, and what are its settings?

No gather rate appears in the name: destiny local test. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on destiny local test?

The game generates a procedural map for destiny local test.

Connection

How do you connect to destiny local test?

Check: join. Open Rust, press F1, then enter client.connect 31.36.131.153:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp8,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp8
Max players Slots: 8.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Build 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.