RUST METRICSFlight deck · live data
Data live Servers11,620 Players35,915 Populated2,914 Fresh wipes 3 h77 Scan5 min
‹ All servers85.131.245.63:28015
Offline Full Queue Fresh wipe Wipe due No query

[JP]TRS:RUST[PvE]

Offline 85.131.245.63:28015 checked 27d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 24 36 48 PAX 0 /48

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#16,728top 70%
Last wipe54d 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 17 Sep. 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 Sep23 Sep27 Sep30 Sep4 Oct7 Oct

Top 70% 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 schedule

What wipe timing does [JP]TRS:RUST[PvE] follow?

To tell the rhythm of [JP]TRS:RUST[PvE], too few of its wipes 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. 54 days 2 hours ago the current world was made.

Tag meanings

Which tags does [JP]TRS:RUST[PvE] carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp48 (Max players): Slots: 48; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Build 162929; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from [JP]TRS:RUST[PvE]. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show [JP]TRS:RUST[PvE]?

These Rust Metrics lists carry [JP]TRS:RUST[PvE]: Modded Rust servers, checked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does [JP]TRS:RUST[PvE] hold among Rust servers?

Ranking for [JP]TRS:RUST[PvE]: #16,728 on seven-day player hours, top 70% of all ranked servers.

What is the population on [JP]TRS:RUST[PvE]?

Reading for [JP]TRS:RUST[PvE]: offline at this moment; last seen 27 days 10 hours ago.

Operator and location

What location is [JP]TRS:RUST[PvE] hosted in?

Reading: location. Nothing in the tags, but the name of [JP]TRS:RUST[PvE] points to Asia. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 85.131.245.63:28015.

What Rust version is [JP]TRS:RUST[PvE] on?

Reading: [JP]TRS:RUST[PvE], Rust network protocol 2633 and build 162929, Linux. Matching protocol is required to join. Let Steam update your game.

What is the uptime on [JP]TRS:RUST[PvE], and is it online?

Reading: offline. [JP]TRS:RUST[PvE] last answered 27 days 10 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

What settings and rules apply on [JP]TRS:RUST[PvE]?

No gather rate appears in the name: [JP]TRS:RUST[PvE]. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

Which map is live on [JP]TRS:RUST[PvE]?

Size 4,000 and seed 1: the game generates the procedural map on [JP]TRS:RUST[PvE] from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto [JP]TRS:RUST[PvE]?

Check: join. Open Rust, press F1, then enter client.connect 85.131.245.63:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp48,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp48
Max players Slots: 48.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs162929
Build Build 162929.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the 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.