RUST METRICSFlight deck · live data
Data live Servers11,802 Players69,058 Populated3,653 Fresh wipes 3 h129 Scan5 min
‹ All servers5.27.25.196:28015
Offline Full Queue Fresh wipe Wipe due No query

[LOCAL] X10

Offline 5.27.25.196:28015 checked 26d ago

10x
COM 1 · connect
Launch Rust and join

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#14,356top 63%
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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 63% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 12:55 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 should you expect from wipe day on [LOCAL] X10?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

What wipe timing does [LOCAL] X10 follow?

To tell the rhythm of [LOCAL] X10, 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 it runs now was made 26 days 8 hours ago.

Tags

Which tags does [LOCAL] X10 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Game build reading: 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from [LOCAL] X10. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does [LOCAL] X10 appear in Rust Metrics lists and filters?

On Rust Metrics, [LOCAL] X10 sits in these lists: 10x Rust servers and 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; Gather rate: 10x.

Player count

What position does [LOCAL] X10 hold among Rust servers?

Ranking for [LOCAL] X10: #14,356 on seven-day player hours, top 63% of all ranked servers.

How full does [LOCAL] X10 get?

Status for [LOCAL] X10: offline. Last seen 26 days 8 hours ago.

Server

Where does [LOCAL] X10 sit?

No region tag on [LOCAL] X10. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 5.27.25.196:28015.

What Rust version is [LOCAL] X10 on?

Reading: [LOCAL] X10, Rust network protocol 2634 and build 166586, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on [LOCAL] X10, and is it online?

[LOCAL] X10 reports offline. The last reading came 26 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Rules and settings

How is [LOCAL] X10 configured, and what rules are in force?

The name carries the rate: 10x gather on [LOCAL] X10. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

What map is [LOCAL] X10 on?

Check: map. Procedural, generated by the game, on [LOCAL] X10.

Join

How can you get onto [LOCAL] X10?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Game build reading: 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.