Working its way up from the back of the class: #15,519 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 434 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
JP_Rust leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 119.83.27.78:28015.
How dependable is JP_Rust, and is it online at the moment?
At this moment, JP_Rust is offline; the last time it was seen was 15 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 9 October 2026, Rust Server Score saw it for the first time.
On what Rust version does JP_Rust sit?
Rust network protocol 2631 and build 156658 on Windows is what JP_Rust runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does JP_Rust wipe its map?
There are too few wipes on record for JP_Rust to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 115 days 10 hours have passed since this world was made.
Population
What position does JP_Rust hold in the rankings?
In the top 71% of all ranked servers, JP_Rust sits at #15,519 for player hours over the last seven days.
Is JP_Rust a busy server?
The last sighting of JP_Rust was 15 days 9 hours ago, and it is offline right now.
Tags
How should you read the tags on JP_Rust?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2631 (Protocol): The game protocol is 2631, so your game must match that version to join; cs156658 (Build): The game build is 156658; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags JP_Rust publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature JP_Rust?
These Rust Server Score lists count JP_Rust among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is JP_Rust set up, and what rules does it keep?
The name of JP_Rust gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map JP_Rust uses?
JP_Rust runs a game-generated procedural map at size 4,000, seed 1234567. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to JP_Rust?
To connect, start Rust, press F1, and type client.connect 119.83.27.78:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://discord.com/channels/1154815332234571981/1364557539605217280.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2631,gmrust,cs156658,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2631
ProtocolThe game protocol is 2631, so your game must match that version to join.
cs156658
BuildThe game build is 156658.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).