RUST METRICSFlight deck · live data
Data live Servers11,703 Players41,069 Populated3,025 Fresh wipes 3 h98 Scan5 min
‹ All servers153.197.161.35:28815
Online Full Queue Fresh wipe Wipe due No query

[JP] まったりクマ鯖 x3 | 10/02 BP Wipe

Online EA 153.197.161.35:28815 checked 10m ago

3x monthly wipes moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 00:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 69 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 110,555 ×1000

Entities

48 h range 103,741–113,045 · memory 3,316 MB
1239 ET SINCE RESTART 03:13

Uptime

3 h 13 min since its last restart, at the last reading
7-day average0peak 3
Rank#5,168top 23% · #381 in EA
Last wipe27d agomonthly schedule
Next wipe7d 17hThu 5 Nov, 19:00 UTC FW
Memory3,316MB48 h peak 3 players
REC 1

Players

AveragePeak
0123402:0011:0020:0005:0014:0000:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020002:0011:0020:0005:0014:0000: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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 23% of all ranked servers, top 68% 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 17h. The force wipe · high confidence

wipe-day peak19players, last three wipes

Coming wipes

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

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 19, 40 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 19:29 UTC FW27d ago 19 – 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] まったりクマ鯖 x3 | 10/02 BP Wipe when wipe day comes?

The busiest point of its recent wipes drew 19 players on average. 40 hours after the wipe, the crowd peaked on the latest wipe.

How often does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe wipe, and when?

Once a month [JP] まったりクマ鯖 x3 | 10/02 BP Wipe wipes, with the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 27 days 6 hours ago the current world was made. The tags state a wipe schedule of one wipe a month.

Tags

How should you read the tags on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

These are the tags [JP] まったりクマ鯖 x3 | 10/02 BP Wipe publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon; EA (East Asia): The server browser files it under East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Who is in charge of [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

Check: operator. [JP] まったりクマ鯖 x3 | 10/02 BP Wipe publishes a crypto-cheer.jp hostname, and 2 other servers we track do too. Same operator, most likely.

Which lists and filters on Rust Metrics show [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

These Rust Metrics lists carry [JP] まったりクマ鯖 x3 | 10/02 BP Wipe: 3x Rust servers, checked live and Modded Rust servers, checked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 3x.

Player count

What position does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe hold among Rust servers?

Top 23% of all ranked servers: [JP] まったりクマ鯖 x3 | 10/02 BP Wipe takes #5,168 on seven-day player hours and #381 in Asia.

How full does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe get?

Current headcount on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe: 0 players, 100 slots available. Seven-day check: 0 players on average. Peak reading: 3. The last 48 hours peaked at 12:00 UTC, averaging 3 players at that hour.

Operator and location

Where does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe sit?

[JP] まったりクマ鯖 x3 | 10/02 BP Wipe gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 153.197.161.35:28815.

What Rust version is [JP] まったりクマ鯖 x3 | 10/02 BP Wipe on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [JP] まったりクマ鯖 x3 | 10/02 BP Wipe. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

Reading: 94 server fps on average across the last 48 hours. It never dropped below 69. Reading: 113,045 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 4,131 MB. Expect lag when fps falls and entities climb.

Is [JP] まったりクマ鯖 x3 | 10/02 BP Wipe up, and how often does it stay up?

[JP] まったりクマ鯖 x3 | 10/02 BP Wipe reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 3 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe enforce, and what are its settings?

Gather rate check: 3x. That comes from the name [JP] まったりクマ鯖 x3 | 10/02 BP Wipe. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

Which map is live on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

From seed 982198303, the game generates the procedural map on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe. Its size is 4,500. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How can you get onto [JP] まったりクマ鯖 x3 | 10/02 BP Wipe?

Check: join. Open Rust, press F1, then enter client.connect 153.197.161.35:28815. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/ZBS9KJStdP.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^z,^y,^m,EA,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Plugin framework in use: Carbon.

Region

EA
East Asia The server browser files it under 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.