RUST METRICSFlight deck · live data
Data live Servers11,621 Players38,053 Populated2,842 Fresh wipes 3 h134 Scan5 min
‹ All servers160.251.136.116:28015
Online Full Queue Fresh wipe Wipe due No query

RustServer_6319

Online 160.251.136.116:28015 checked 10m ago

COM 1 · connect

Server instruments

last reading Fri 04:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 145 SERVER FPS

Server fps

48 h low 128 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 43,515 ×1000

Entities

48 h range 41,423–43,830 · memory 2,656 MB
1239 ET SINCE RESTART 8D 18H

Uptime

8 days 18 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,270top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Memory2,656MBat the last reading
REC 1

Players

AveragePeak
0123406:0015:0001:0010:0019:0004:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040006:0015:0001:0010:0019:0004:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 69% 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.

usual gap18.8 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctSun 13 Sep
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, 13:30 UTC27d ago 0 – running 0
Sun 13 Sep, 19:14 UTC46d ago 0 – 18.8 days 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 happens on RustServer_6319 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.

When does RustServer_6319 wipe?

Its rhythm cannot be told from the wipes of RustServer_6319 on record: there are too few. 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 27 days 15 hours ago.

Tag meanings

Which tags does RustServer_6319 carry, and what do they mean?

Tags published by RustServer_6319, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is 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 RustServer_6319?

On Rust Metrics, RustServer_6319 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does RustServer_6319 hold among Rust servers?

Ranking for RustServer_6319: #15,270 on seven-day player hours, top 69% of all ranked servers.

How full does RustServer_6319 get?

0 of 50 slots are filled on RustServer_6319 right now. A seven-day average of 0 players is the reading.

Server details

Which location does RustServer_6319 run from?

Reading: location. RustServer_6319 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.251.136.116:28015.

What Rust version is RustServer_6319 on?

Rust network protocol 2634 and build 167781 on Linux is the build RustServer_6319 runs. Matching protocol is required to join. Let Steam update your game.

How does RustServer_6319 perform?

Over the last 48 hours the average was 181 server fps; the floor was 128. Reading: 43,830 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 2,656 MB. What players call lag comes from low fps and an entity count on the rise.

Is RustServer_6319 up, and how often does it stay up?

Reading: online. RustServer_6319 answers right now. Check: restart. The uptime it reports puts the last restart about 8 days 18 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What rules does RustServer_6319 enforce, and what are its settings?

No gather rate appears in the name: RustServer_6319. 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. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on RustServer_6319?

Check: map. Procedural, size 3,000, seed 26771, generated by the game on RustServer_6319. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to RustServer_6319?

Press F1 in Rust and enter client.connect 160.251.136.116:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.