RUST METRICSFlight deck · live data
Data live Servers11,801 Players73,164 Populated3,682 Fresh wipes 3 h113 Scan5 min
‹ All servers129.222.59.31:28015
Offline Full Queue Fresh wipe Wipe due No query

JDAVID56

Offline 129.222.59.31:28015 checked 20d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 2 /10

Players now

20% 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#12,140top 55%
Last wipe21d 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 55% 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 peak2players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 19:52 UTC21d ago 2 – running 1

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 JDAVID56 when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 2 hours.

What wipe timing does JDAVID56 follow?

Its rhythm cannot be told from the wipes of JDAVID56 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. 21 days 1 hours ago the current world was made.

Tag meanings

How should you read the tags on JDAVID56?

Tags published by JDAVID56, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167058 (Build): The server runs game build 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. 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 JDAVID56?

On Rust Metrics, JDAVID56 sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does JDAVID56 hold among Rust servers?

Ranking for JDAVID56: #12,140 on seven-day player hours, top 55% of all ranked servers.

How full does JDAVID56 get?

Reading for JDAVID56: offline at this moment; last seen 20 days 20 hours ago.

Operator and location

Where does JDAVID56 sit?

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

What Rust version is JDAVID56 on?

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

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

Check: connection. JDAVID56 is offline at this moment. Last contact was 20 days 20 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 7 October 2026.

Settings and map

What settings and rules apply on JDAVID56?

Check: gather rate. The name JDAVID56 does not state one. 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. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is JDAVID56 on?

The game generates a procedural map for JDAVID56.

Join

What do you do to join JDAVID56?

To join: start Rust, press F1 and type client.connect 129.222.59.31: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,gmvanilla,cs167058,ts8,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167058
Build The server runs game build 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.