Rust Data

rustdata.spaceservers157.85.94.71:20893.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.94.71:20892 checked 11m ago

JDMEASY

moddedoxide

Connect

srv = rust.server("157.85.94.71:20893")
print(srv.connect_command)

Right now

srv.summary()
players now 0/75 # 0% full
7-day average 0 # peak 3
rank #5,894 # top 27%
last wipe 2d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123400:0006:0012:0017:0023:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020000:0006:0012:0017:0023:0022: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 25 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 23:16 UTC2d ago NaN NaN running 1
1 Sun 25 Oct, 19:49 UTC3d ago 3 NaN 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.

display(srv.map, srv.info())

Map

4000 · seed 319899182
Map of JDMEASY
map
Procedural Map
size
4000
seed
319899182
Open on RustMaps

Server

srv.info()
address
157.85.94.71:20892
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 23:16 UTC
hostname
–
first seen
25 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average55/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average46/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average54/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average7/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average8/1000

Quick answers

From the figures on this page.

Population data

How does JDMEASY compare in the rankings?

Over the last seven days JDMEASY sits at #5,894 on player hours, in the top 27% of ranked servers.

What population does JDMEASY carry?

Current row: 0 players on JDMEASY, against 75 slots. Over the last seven days it averaged 0 players and peaked at 3. Averaged by hour over 48 hours, 00:00 UTC is the busiest, at 3 players.

Server facts

How well does JDMEASY perform?

Averaged over 48 hours: 105 server fps, never under 89. The entity count peaked at 94,137, covering buildings, deployables and the rest of the world. The memory field tops out at 4,201 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is JDMEASY on?

The build is Rust network protocol 2635 and build 168909 on Linux, run by JDMEASY. Joining needs the same protocol on your game; Steam handles the update.

How reliable is JDMEASY, and is it up?

The current sample puts JDMEASY online. Count back 2 hours from its reported uptime to get the last restart. Uptime of 100% across the last 2 full days: 48 hours of 48. Its earliest recorded date in Rust Data is 25 October 2026.

Where does JDMEASY sit?

There is no region published for JDMEASY. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 157.85.94.71:20892.

Settings and map

Which rules apply on JDMEASY, and what settings?

No gather rate appears in the name: JDMEASY. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

Which map has JDMEASY loaded?

JDMEASY runs a procedural map of size 4,000 with seed 319899182, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

On what schedule does JDMEASY wipe?

The record for JDMEASY holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 2 days ago.

What is wipe day on JDMEASY like?

Across recent wipes the busiest point averaged 3 players. 3 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does JDMEASY appear among Rust Data lists and filters?

The Rust Data lists that JDMEASY fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on JDMEASY hold?

The game's server browser reads these tags from JDMEASY: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): 75 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to JDMEASY?

In Rust, F1 opens the console: type client.connect 157.85.94.71:20892. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp75
Max players 75 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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.

Rust Data 53,534 players 11,735 servers online