RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h37 Scan5 min
‹ All servers157.85.94.71:20892
Offline Full Queue Fresh wipe Wipe due No query

JDMEASY

Offline 157.85.94.71:20892 checked 17h ago

moddedoxide
COM 1 · connect

Server instruments

last reading Wed 01:00 UTC
0 19 38 56 75 PAX 1 /75

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 89 SERVER FPS

Server fps

48 h low 89 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 94,137 ×1000

Entities

48 h range 79,535–94,137 · memory 3,300 MB
1239 ET SINCE RESTART 07:38

Uptime

7 h 38 min since its last restart, at the last reading
7-day average0peak 3
Rank#6,074top 27%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
Memory3,300MB48 h peak 3 players
REC 1

Players

AveragePeakWipe
0123420:0002:0008:0013:0019:0001:00Wiped Mon 26 Oct, 23:16 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020020:0002:0008:0013:0019:0001:00Wiped Mon 26 Oct, 23:16 UTCWIPE

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 25 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct

Top 27% 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 gap1.1 daysbetween real wipes
wipe-day peak3players, 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 3, 3 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 23:16 UTC1d ago – – running 1
Sun 25 Oct, 19:49 UTC2d ago 3 – 1.1 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 JDMEASY when wipe day comes?

The busiest point of its recent wipes drew 3 players on average. 3 hours after the wipe, the crowd peaked on the latest wipe.

How often does JDMEASY wipe, and when?

The rhythm of JDMEASY'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. The world in play was created 44 hours ago.

Tag meanings

How should you read the tags on JDMEASY?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp75 (Max players): Slots: 75; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 from JDMEASY. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show JDMEASY?

These Rust Metrics lists carry JDMEASY: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does JDMEASY sit in the rankings?

Ranking for JDMEASY: #6,074 on seven-day player hours, top 27% of all ranked servers.

How full does JDMEASY get?

Reading for JDMEASY: offline at this moment; last seen 17 hours ago. Check: players over seven days. Average 0, peak 3. The last 48 hours peaked at 00:00 UTC, averaging 3 players at that hour.

Server details

Where does JDMEASY sit?

Reading: location. JDMEASY gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 157.85.94.71:20892.

What Rust version is JDMEASY on?

Reading: JDMEASY, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does JDMEASY perform?

Reading: 108 server fps on average across the last 48 hours. It never dropped below 89. Reading: 94,137 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,201 MB. Expect lag when fps falls and entities climb.

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

Reading: offline. JDMEASY last answered 17 hours ago. Check: restart. The uptime it reports puts the last restart about 7 hours ago. Uptime for the last 2 full days: 48 of 48 hours, or 100%. The first sighting on Rust Metrics was 25 October 2026.

Map and rules

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

No gather rate appears in the name: JDMEASY. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on JDMEASY?

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

How to join

What do you do to join JDMEASY?

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

PLACARDS

Server tags

what each one means

Published as mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp75
Max players Slots: 75.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.