RUST METRICSFlight deck · live data
Data live Servers11,673 Players48,102 Populated3,006 Fresh wipes 3 h99 Scan5 min
‹ All servers163.44.143.51:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_8510

Offline 163.44.143.51:28015 checked 6d ago

moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,269top 69%
Last wipe11d 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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct14 Oct19 Oct25 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 gap8.2 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Sun 18 OctFri 9 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 03:18 UTC11d ago 1 – running 0
Fri 9 Oct, 23:42 UTC20d ago 1 halved by day 3 8.2 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 should you expect from wipe day on RustServer_8510?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 3 when it didn't.

When does RustServer_8510 wipe?

The rhythm of RustServer_8510's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 11 days 23 hours ago the current world was made.

Tag meanings

How should you read the tags on RustServer_8510?

These are the tags RustServer_8510 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RustServer_8510?

These Rust Metrics lists carry RustServer_8510: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does RustServer_8510 sit in the rankings?

Player hours over seven days put RustServer_8510 at #15,269, in the top 69% of all ranked servers.

What is the population on RustServer_8510?

Reading for RustServer_8510: offline at this moment; last seen 6 days 21 hours ago. Check: player average. 0 over the last seven days.

Server details

Where does RustServer_8510 sit?

No region tag on RustServer_8510. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 163.44.143.51:28015.

What Rust version is RustServer_8510 on?

Reading: RustServer_8510, Rust network protocol 2634 and build 166652, Linux. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. RustServer_8510 last answered 6 days 21 hours ago. Reading: 4% uptime over the last 7 full days. It was up 6 of 168 hours. The first sighting on Rust Metrics was 3 October 2026.

Settings and map

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

Check: gather rate. The name RustServer_8510 does not state one. The group cap is 8 players, which is the default in the game. pve, fighting between players is off — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_8510 on?

Size 3,700 and seed 18382: the game generates the procedural map on RustServer_8510 from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to RustServer_8510?

Press F1 in Rust and enter client.connect 163.44.143.51: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,^p,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.