RUST METRICSFlight deck · live data
Data live Servers11,722 Players56,412 Populated3,390 Fresh wipes 3 h135 Scan5 min
‹ All servers119.83.27.78:28015
Offline Full Queue Fresh wipe Wipe due No query

JP_Rust

Offline 119.83.27.78:28015 checked 15d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

0% 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#15,519top 71%
Last wipe115d agono schedule published
Next wipe–no wipe 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, measured since 9 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
15k10k15k20k9 Oct11 Oct13 Oct15 Oct17 Oct19 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

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 wipe timing does JP_Rust follow?

The rhythm of JP_Rust's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 115 days 9 hours ago.

Tag meanings

How should you read the tags on JP_Rust?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2631 (Protocol): Your game must run protocol 2631 to get in; cs156658 (Build): The server runs game build 156658; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from JP_Rust. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does JP_Rust appear in Rust Metrics lists and filters?

Rust Metrics lists featuring JP_Rust: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does JP_Rust hold among Rust servers?

Ranking for JP_Rust: #15,519 on seven-day player hours, top 71% of all ranked servers.

How full does JP_Rust get?

JP_Rust is not responding; status offline, last seen 15 days 7 hours ago.

Server details

What location is JP_Rust hosted in?

No region tag on JP_Rust. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 119.83.27.78:28015.

What Rust version is JP_Rust on?

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

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

Reading: offline. JP_Rust last answered 15 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Map and rules

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

No gather rate appears in the name: JP_Rust. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is JP_Rust on?

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

Connection

How do you connect to JP_Rust?

Press F1 in Rust and enter client.connect 119.83.27.78:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://discord.com/channels/1154815332234571981/1364557539605217280 is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2631,gmrust,cs156658,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2631
Protocol Your game must run protocol 2631 to get in.
cs156658
Build The server runs game build 156658.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.