RUST METRICSFlight deck · live data
Data live Servers11,664 Players42,799 Populated3,021 Fresh wipes 3 h89 Scan5 min
‹ All servers106.73.3.64:28015
Offline Full Queue Fresh wipe Wipe due No query

JP Server

Offline 106.73.3.64:28015 checked 10d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

10% 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#12,999top 60%
Last wipe25d agono schedule published
Next wipe–too few wipes 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct10 Oct17 Oct24 Oct

Top 60% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 11:36 UTC25d ago 1 – running 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

Reset cycle

What happens on JP Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does JP Server wipe, and when?

Its rhythm cannot be told from the wipes of JP Server on record: there are too few. 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 in play was created 25 days 14 hours ago.

Tag meanings

How should you read the tags on JP Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167058 (Build): Game build reading: 167058; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from JP Server. 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 JP Server?

These Rust Metrics lists carry JP Server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does JP Server sit in the rankings?

Player hours over seven days put JP Server at #12,999, in the top 60% of all ranked servers.

What is the population on JP Server?

Status for JP Server: offline. Last seen 10 days 17 hours ago.

Operator and location

Which location does JP Server run from?

Reading: location. Nothing in the tags, but the name of JP Server points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 106.73.3.64:28015.

What Rust version is JP Server on?

Rust network protocol 2634 and build 167058 on Windows is the build JP Server runs. Matching protocol is required to join. Let Steam update your game.

How reliable is JP Server, and is it online now?

Check: connection. JP Server is offline at this moment. Last contact was 10 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is JP Server configured, and what rules are in force?

No gather rate appears in the name: JP Server. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on JP Server?

The game generates a procedural map for JP Server.

How to join

What do you do to join JP Server?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167058
Build Game build reading: 167058.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^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.