Rust Server Analytics 60,429 players11,767 servers
All servers
Drill-through Server detail

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

Online EA 153.197.161.35:28815 checked 9m ago

Drill-through
FilterServeris [JP] まったりクマ鯖 x3 | 10/02 BP Wipe
Attributes
3x monthly wipes moddedcarbon
Last refreshed
Players now 0/ 100
7-day average 0 peak 3
Rank #5,168 top 23% · #381 in EA
Last wipe 27d ago monthly schedule
Next wipe 7d 20h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123423:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020023:0008:0017:0002:0011:0021: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.

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule

force wipes only

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

wipe-day peak19players, last three wipes

Coming wipes

InWhen, UTCKind
7d 20hThu 5 Nov, 19:00 UTCFW force wipe
35d 20hThu 3 Dec, 19:00 UTCFW force wipe

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.

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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long EA · groups of 100+ · 3x · monthly · 7 on average 4 / 120
HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP EA · groups of 8+ · 3x · monthly · 2 on average 0 / 75
Japan Tokyo - Limited Raid Hours |3x|PvP|JP EA · groups of 8+ · 3x · weekly · 40 on average 6 / 300
#5[坚果]2X Solo/独狼/萌新/养老/月清 EA · no group limit · 2x · monthly · 3 on average 0 / 500
[ASIA] RustSEA+|Xtra Modded|Pure PVE|2x|No Purge|EXP Leveling|E EA · groups of 8+ · 2x · monthly · 2 on average 0 / 50
초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3 EA · groups of 8+ · 3x · 1 on average 0 / 50

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for [JP] まったりクマ鯖 x3 | 10/02 BP Wipe: what is it?

With the force wipe, once a month, [JP] まったりクマ鯖 x3 | 10/02 BP Wipe wipes. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The current world dates from 27 days 3 hours. The tags carry a monthly wipe schedule.

On [JP] まったりクマ鯖 x3 | 10/02 BP Wipe, what happens on wipe day?

Across recent wipes the busiest point averaged 19 players. The highest player count on the latest wipe arrived 40 hours in.

Server details

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

In Asia, according to its EA tag, sits [JP] まったりクマ鯖 x3 | 10/02 BP Wipe. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 153.197.161.35:28815 is its address.

What Rust build does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe run?

On Linux, [JP] まったりクマ鯖 x3 | 10/02 BP Wipe runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.

Is [JP] まったりクマ鯖 x3 | 10/02 BP Wipe up, and how steady is its uptime?

The current status of [JP] まったりクマ鯖 x3 | 10/02 BP Wipe is online. Its reported uptime indicates a restart roughly 13 minutes ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.

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

Over 48 hours the average held at 94 server fps, and the minimum was 69. Buildings, deployables and all other world objects brought the entity total to 113,045. Memory use reached 4,131 MB at peak. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

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

Tags from [JP] まったりクマ鯖 x3 | 10/02 BP Wipe, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Capacity of 100 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^m (Monthly): Monthly wipes, aligned with the force wipe; ^z (Modded): The Modded section, because plugins or settings modify play; ^y (Carbon): It runs Carbon for plugins; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count [JP] まったりクマ鯖 x3 | 10/02 BP Wipe among their servers: 3x Rust servers: live list and Modded Rust servers: live data. On the server list, the filters that return it are: Region: Asia; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 3x.

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

A crypto-cheer.jp hostname is published by [JP] まったりクマ鯖 x3 | 10/02 BP Wipe, as by 2 other servers we track, so one operator most likely runs them all.

Population

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

For player hours over the last seven days, [JP] まったりクマ鯖 x3 | 10/02 BP Wipe places #5,168 globally and #381 in Asia, in the top 23% of all ranked servers.

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

Of 100 slots, 0 are filled on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe at this refresh. The seven-day mean is 0 players, against a peak of 3. The 48-hour peak window is 12:00 UTC, at an average of 3 players.

Map and rules

What settings and rules does [JP] まったりクマ鯖 x3 | 10/02 BP Wipe use?

[JP] まったりクマ鯖 x3 | 10/02 BP Wipe names a 3x gather rate. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. Plugins from Carbon are in use. Anti-cheat status: VAC on.

The map on [JP] まったりクマ鯖 x3 | 10/02 BP Wipe: which one is it?

The game generates a procedural map of size 4,500 with seed 982198303 for [JP] まったりクマ鯖 x3 | 10/02 BP Wipe. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

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

In the Rust console (F1), enter client.connect 153.197.161.35:28815. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://discord.com/invite/ZBS9KJStdP is its website.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Capacity of 100 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code The region code is blank.

Wipe schedule

^m
Monthly Monthly wipes, aligned with the force wipe.

Mods and access

^z
Modded The Modded section, because plugins or settings modify play.
^y
Carbon It runs Carbon for plugins.

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.