RUST METRICSFlight deck · live data
Data live Servers11,761 Players76,398 Populated3,723 Fresh wipes 3 h136 Scan5 min
‹ All servers89.93.135.111:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust local - test

Offline 89.93.135.111:28015 checked 26d ago

COM 1 · connect

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#13,819top 60%
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
15k10k15k20k28 Sep30 Sep2 Oct5 Oct7 Oct9 Oct

Top 60% 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, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 02:03 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 schedule

What happens on Rust local - test when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 2 hours in.

What wipe timing does Rust local - test follow?

To tell the rhythm of Rust local - test, 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 26 days 11 hours ago.

Lists and filters

How should you read the tags on Rust local - test?

Tags published by Rust local - test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

These Rust Metrics lists carry Rust local - test: 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 Rust local - test hold among Rust servers?

Ranking for Rust local - test: #13,819 on seven-day player hours, top 60% of all ranked servers.

How full does Rust local - test get?

Reading for Rust local - test: offline at this moment; last seen 26 days 8 hours ago.

Operator and location

Which location does Rust local - test run from?

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

What Rust version is Rust local - test on?

Rust network protocol 2634 and build 166494 on Windows is the build Rust local - test runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. Rust local - test is offline at this moment. Last contact was 26 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 28 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Rust local - test?

Reading the name gives no gather rate for Rust local - test. No limit is set beyond the default. Groups take up to 8 players. 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. Anti-cheat reading: VAC off, Valve's system.

Which map is live on Rust local - test?

Check: map. Procedural, generated by the game, on Rust local - test.

Join

What do you do to join Rust local - test?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Build 166494.
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.