RUST METRICSFlight deck · live data
Data live Servers11,793 Players79,700 Populated3,567 Fresh wipes 3 h247 Scan5 min
‹ All servers188.29.127.108:28215
Offline Full Queue Fresh wipe Wipe due No query

LOCAL-TEST-DO-NOT-JOIN

Offline 188.29.127.108:28215 checked 30d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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#16,882top 71%
Last wipe30d 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
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 11:14 UTC30d 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

Wipe timing

What should you expect from wipe day on LOCAL-TEST-DO-NOT-JOIN?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does LOCAL-TEST-DO-NOT-JOIN follow?

To tell the rhythm of LOCAL-TEST-DO-NOT-JOIN, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 30 days 11 hours ago.

Tags

How should you read the tags on LOCAL-TEST-DO-NOT-JOIN?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from LOCAL-TEST-DO-NOT-JOIN. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does LOCAL-TEST-DO-NOT-JOIN appear in Rust Metrics lists and filters?

Rust Metrics lists featuring LOCAL-TEST-DO-NOT-JOIN: 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.

Player count

Where does LOCAL-TEST-DO-NOT-JOIN sit in the rankings?

Ranking for LOCAL-TEST-DO-NOT-JOIN: #16,882 on seven-day player hours, top 71% of all ranked servers.

How full does LOCAL-TEST-DO-NOT-JOIN get?

Reading for LOCAL-TEST-DO-NOT-JOIN: offline at this moment; last seen 30 days 11 hours ago.

Server

Which location does LOCAL-TEST-DO-NOT-JOIN run from?

No region comes from LOCAL-TEST-DO-NOT-JOIN. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 188.29.127.108:28215.

What Rust version is LOCAL-TEST-DO-NOT-JOIN on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by LOCAL-TEST-DO-NOT-JOIN. To get in, your game needs the same protocol; Steam applies the update.

How reliable is LOCAL-TEST-DO-NOT-JOIN, and is it online now?

Check: connection. LOCAL-TEST-DO-NOT-JOIN is offline at this moment. Last contact was 30 days 11 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 29 September 2026.

Map and rules

What rules does LOCAL-TEST-DO-NOT-JOIN enforce, and what are its settings?

No gather rate appears in the name: LOCAL-TEST-DO-NOT-JOIN. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is LOCAL-TEST-DO-NOT-JOIN on?

Procedural map on LOCAL-TEST-DO-NOT-JOIN, made by the game's generator.

How to join

How do you connect to LOCAL-TEST-DO-NOT-JOIN?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players Slots: 2.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.