RUST METRICSFlight deck · live data
Data live Servers11,634 Players56,511 Populated3,185 Fresh wipes 3 h139 Scan5 min
‹ All servers183.251.116.191:28015
Offline Full Queue Fresh wipe Wipe due No query

鑰佺櫧鏈嶅姟鍣? ^

Offline 183.251.116.191:28015 checked 27d ago

COM 1 · connect

Server instruments

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

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#15,905top 70%
Last wipe27d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 12:39 UTC27d 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 schedule

What happens on 鑰佺櫧鏈嶅姟鍣? ^ when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does 鑰佺櫧鏈嶅姟鍣? ^ follow?

The rhythm of 鑰佺櫧鏈嶅姟鍣? ^'s wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 27 days 18 hours ago.

Tag meanings

How should you read the tags on 鑰佺櫧鏈嶅姟鍣? ^?

These are the tags 鑰佺櫧鏈嶅姟鍣? ^ publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): 4 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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 Metrics lists featuring 鑰佺櫧鏈嶅姟鍣? ^: Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does 鑰佺櫧鏈嶅姟鍣? ^ hold among Rust servers?

Ranking for 鑰佺櫧鏈嶅姟鍣? ^: #15,905 on seven-day player hours, top 70% of all ranked servers.

What player count does 鑰佺櫧鏈嶅姟鍣? ^ carry?

Reading for 鑰佺櫧鏈嶅姟鍣? ^: offline at this moment; last seen 27 days 18 hours ago.

Operator and location

Where does 鑰佺櫧鏈嶅姟鍣? ^ sit?

Reading: location. Nothing in the tags, but the name of 鑰佺櫧鏈嶅姟鍣? ^ points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 183.251.116.191:28015.

What Rust version is 鑰佺櫧鏈嶅姟鍣? ^ on?

Reading: 鑰佺櫧鏈嶅姟鍣? ^, Rust network protocol 2634 and build 166586, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is 鑰佺櫧鏈嶅姟鍣? ^, and is it online now?

Check: connection. 鑰佺櫧鏈嶅姟鍣? ^ is offline at this moment. Last contact was 27 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 2 October 2026.

Map and rules

What settings and rules apply on 鑰佺櫧鏈嶅姟鍣? ^?

Check: gather rate. The name 鑰佺櫧鏈嶅姟鍣? ^ does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. 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 on.

Which map is live on 鑰佺櫧鏈嶅姟鍣? ^?

The game generates a procedural map for 鑰佺櫧鏈嶅姟鍣? ^.

Join

How do you connect to 鑰佺櫧鏈嶅姟鍣? ^?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players 4 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166586
Build Build 166586.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.