On the class lists: D (51), with population over 48 hours and no performance mark.
Players now1/ 751% full
7-day average0peak 3
Rank#6,092top 27%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 75 on average. Plenty of space to grow.
Standingrank on player hours
73/ 100
B−
Holds a respectable place: #6,092 on player hours.
Uptimehours on the list, last 48
79/ 100
B
Missed a few lessons: on the list 38 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 97 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 27% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
W··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 3, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for JDMEASY. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 157.85.94.71:20892.
Is JDMEASY up, and how steady is its uptime?
At this moment, JDMEASY is offline; the last time it was seen was 9 hours ago. The uptime it reports puts the last restart at about 7 hours ago. It was up 48 of 48 hours over the last 2 full days, which is 100% of the time. On 25 October 2026, Rust Server Score saw it for the first time.
How well does JDMEASY run?
The average over the last 48 hours was 97 server fps, and it never went below 1. Up to 94,157 entities were in the world, covering buildings, deployables and the rest. Up to 4,201 MB of memory was used. When fps is low and entities climb, that is lag to players.
What Rust version is JDMEASY on?
You will find JDMEASY on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does JDMEASY reset?
The record holds too few of JDMEASY's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 35 hours.
What happens on JDMEASY when wipe day arrives?
Recent wipes have peaked at 3 players on average. The crowd on the latest wipe was largest 3 hours after it began.
Player count
Where does JDMEASY place in the wider field of Rust servers?
Over the last seven days, JDMEASY has #6,092 for player hours, in the top 27% of all ranked servers.
Is JDMEASY a busy server?
It has been 9 hours since JDMEASY was last seen, and it is offline right now. It peaked at 3 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 00:00 UTC, with an average of 3 players.
Tags
What is meant by the tags on JDMEASY?
You'll see JDMEASY tagged with gmrust (Game mode): Survival in the standard Rust style; mp75 (Max players): Its slot count is 75; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show JDMEASY?
These Rust Server Score lists count JDMEASY among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Server rules
Which rules does JDMEASY enforce, and what are its settings?
You will find no gather rate in the name of JDMEASY. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on JDMEASY?
A procedural map of size 4,000 and seed 319899182, generated by the game, is what JDMEASY runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to JDMEASY?
To connect, start Rust, press F1, and type client.connect 157.85.94.71:20892. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp75
Max playersIts slot count is 75.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).