RUST METRICSFlight deck · live data
Data live Servers11,621 Players32,314 Populated2,788 Fresh wipes 3 h69 Scan5 min
‹ All servers218.166.173.143:28015
Offline Full Queue Fresh wipe Wipe due No query

1919810

Offline 218.166.173.143:28015 checked 34d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,749top 71%
Last wipe34d 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
15k10k15k20k24 Sep25 Sep27 Sep28 Sep30 Sep1 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

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
Thu 24 Sep, 14:10 UTC34d 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

Reset cycle

What should you expect from wipe day on 1919810?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does 1919810 follow?

To tell the rhythm of 1919810, too few of its wipes 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 34 days 14 hours ago.

Tags

How should you read the tags on 1919810?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from 1919810. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does 1919810 appear in Rust Metrics lists and filters?

On Rust Metrics, 1919810 sits in these lists: 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.

Player count

Where does 1919810 sit in the rankings?

Ranking for 1919810: #15,749 on seven-day player hours, top 71% of all ranked servers.

What player count does 1919810 carry?

Status for 1919810: offline. Last seen 34 days 13 hours ago.

Operator and location

Where does 1919810 sit?

No region tag on 1919810. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 218.166.173.143:28015.

What Rust version is 1919810 on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by 1919810. Matching protocol is required to join. Let Steam update your game.

What is the uptime on 1919810, and is it online?

Check: connection. 1919810 is offline at this moment. Last contact was 34 days 13 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 24 September 2026.

Rules and settings

How is 1919810 configured, and what rules are in force?

Reading the name gives no gather rate for 1919810. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. 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.

What map is 1919810 on?

The game generates a procedural map for 1919810.

Connection

How can you get onto 1919810?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.