RUST METRICSFlight deck · live data
Data live Servers11,791 Players65,961 Populated3,606 Fresh wipes 3 h126 Scan5 min
‹ All servers110.4.143.100:28015
Online Full Queue Fresh wipe Wipe due No query

[JP][PVE] パグさば Pug-Server ver 27 | 10/2~

Online EA 110.4.143.100:28015 checked 12m ago

moddedcarbonpve
COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 25 50 75 100 PAX 6 /100

Players now

6% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 53 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 234,836 ×1000

Entities

48 h range 234,836–241,299 · memory 6,366 MB
1239 ET SINCE RESTART 20:03

Uptime

20 h 3 min since its last restart, at the last reading
7-day average14peak 36
Rank#777top 3% · #54 in EA
Last wipe27d agono schedule published
Next wipe7d 20hThu 5 Nov, 19:00 UTC FW
Memory6,366MB48 h peak 34 players
REC 1

Players

AveragePeak
01020304023:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608023:0008:0017:0001:0010:0020:00

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
12505007501k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 3% of all ranked servers, top 10% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. The force wipe · high confidence

wipe-day peak70players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 20hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 20hFW

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 70, 45 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:09 UTC FW27d ago 70 – running 10

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 happens on [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ when wipe day comes?

The busiest point of its recent wipes drew 70 players on average. After the latest wipe, numbers topped out at 45 hours.

How often does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ wipe, and when?

Once a month [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ wipes, with the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 27 days 3 hours ago.

Lists and filters

Which tags does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ carry, and what do they mean?

Tags published by [JP][PVE] パグさば Pug-Server ver 27 | 10/2~, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts16 (Group limit): Team cap: 16; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here; EA (East Asia): Its browser listing: East Asia. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ appear in Rust Metrics lists and filters?

On Rust Metrics, [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ sits in these lists: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Average players: 10+ on average.

Occupancy

Where does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ sit in the rankings?

Ranked by seven-day player hours, [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ sits at #777 and #54 in Asia, inside the top 3%.

What is the population on [JP][PVE] パグさば Pug-Server ver 27 | 10/2~?

Current headcount on [JP][PVE] パグさば Pug-Server ver 27 | 10/2~: 6 players, 100 slots available. Check: players over seven days. Average 14, peak 36. The last 48 hours peaked at 13:00 UTC, averaging 29 players at that hour.

Server details

Which location does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ run from?

Its EA tag places [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 110.4.143.100:28015.

What Rust version is [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by [JP][PVE] パグさば Pug-Server ver 27 | 10/2~. To get in, your game needs the same protocol; Steam applies the update.

How does [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ perform?

Reading: 59 server fps on average across the last 48 hours. It never dropped below 53. Peak entity count: 241,299. Buildings, deployables and all else included. Check: memory. Peak use was 6,673 MB. Expect lag when fps falls and entities climb.

Is [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ up, and how often does it stay up?

Reading: online. [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ answers right now. Reading: uptime. About 20 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

How is [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ configured, and what rules are in force?

No gather rate appears in the name: [JP][PVE] パグさば Pug-Server ver 27 | 10/2~. The cap on groups is 16 players. Mode check gives pve; other players are not fought. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is [JP][PVE] パグさば Pug-Server ver 27 | 10/2~ on?

From seed 1440274916, the game generates the procedural map on [JP][PVE] パグさば Pug-Server ver 27 | 10/2~. Its size is 4,250. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: 初心者もウェルカム!.

How to join

What do you do to join [JP][PVE] パグさば Pug-Server ver 27 | 10/2~?

Press F1 in Rust and enter client.connect 110.4.143.100:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/jGpU2tgxU7.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,EA,^z,^y,^p,gmrust,cs168909,ts16

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts16
Group limit Team cap: 16.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

Region

EA
East Asia Its browser listing: East Asia.

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.