RUST METRICSFlight deck · live data
Data live Servers11,662 Players33,506 Populated2,814 Fresh wipes 3 h80 Scan5 min
‹ All servers118.27.225.83:28015
Online Full Queue Fresh wipe Wipe due No query

[JP]初心者 | momoserver | 10/16 | PVP

Online 118.27.225.83:28015 checked 13m ago

biweekly wipes
COM 1 · connect

Server instruments

last reading Thu 02:00 UTC
0 15 30 45 60 PAX 0 /60

Players now

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

Server fps

48 h low 62 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 97,772 ×1000

Entities

48 h range 97,772–107,265 · memory 2,595 MB
1239 ET SINCE RESTART 12:23

Uptime

12 h 23 min since its last restart, at the last reading
7-day average9peak 42
Rank#1,030top 5%
Last wipe12d agobiweekly schedule
Next wipe1d 8hFri 30 Oct, 12:36 UTC
Memory2,595MB48 h peak 16 players
REC 1

Players

AveragePeak
0510152005:0014:0023:0007:0016:0002:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020005:0014:0023:0007:0016:0002: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
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 5% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 12:36 UTC, in 1d 8h. Its biweekly schedule tag · low confidence

usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak46players, last three wipes
crowd held0%else halves by day 9

Coming wipes

  1. WPT 1Fri 30 Oct, 12:36 UTC1d 8h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 14hFW
  3. WPT 3Fri 13 Nov, 12:36 UTC15d 8h
  4. WPT 4Fri 27 Nov, 12:36 UTC29d 8h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 14hFW
  6. WPT 6Fri 11 Dec, 12:36 UTC43d 8h

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 41, 27 hours in, with 3 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 12:36 UTC12d ago 41+3 queue – running 9
Fri 2 Oct, 11:18 UTC26d ago 48+1 queue halved by day 7 14.1 days 0
Fri 18 Sep, 14:09 UTC40d ago 50+16 queue halved by day 11 13.9 days 1

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 timing

What should you expect from wipe day on [JP]初心者 | momoserver | 10/16 | PVP?

The busiest point of its recent wipes drew 46 players on average. With 3 more waiting in the queue, the crowd peaked 27 hours after the wipe on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 9 it fell below half when it didn't.

How often does [JP]初心者 | momoserver | 10/16 | PVP wipe, and when?

The prediction follows its tag, because too few of [JP]初心者 | momoserver | 10/16 | PVP's wipes are on record to confirm its schedule. Friday 30 October at 12:36 UTC is when its next wipe is due. 12 days 15 hours ago the current world was made. The tags carry an every-two-weeks wipe schedule.

Lists and filters

How should you read the tags on [JP]初心者 | momoserver | 10/16 | PVP?

Tags published by [JP]初心者 | momoserver | 10/16 | PVP, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp60 (Max players): Slots: 60; ts6 (Group limit): Teams are capped at 6; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): It wipes once a fortnight. 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]初心者 | momoserver | 10/16 | PVP?

Rust Metrics lists featuring [JP]初心者 | momoserver | 10/16 | PVP: Rust community servers: live readings. Check: filters. On the server list it appears under these: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Population

What position does [JP]初心者 | momoserver | 10/16 | PVP hold among Rust servers?

Player hours over seven days put [JP]初心者 | momoserver | 10/16 | PVP at #1,030, in the top 5% of all ranked servers.

How full does [JP]初心者 | momoserver | 10/16 | PVP get?

Current headcount on [JP]初心者 | momoserver | 10/16 | PVP: 0 players, 60 slots available. Check: players over seven days. Average 9, peak 42. The last 48 hours peaked at 12:00 UTC, averaging 15 players at that hour.

Server details

Which location does [JP]初心者 | momoserver | 10/16 | PVP run from?

Check: location. No region tag comes from [JP]初心者 | momoserver | 10/16 | PVP, but the name points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 118.27.225.83:28015.

What Rust version is [JP]初心者 | momoserver | 10/16 | PVP on?

Rust network protocol 2635 and build 168909 on Linux is the build [JP]初心者 | momoserver | 10/16 | PVP runs. Matching protocol is required to join. Let Steam update your game.

Is performance on [JP]初心者 | momoserver | 10/16 | PVP within range?

Over the last 48 hours the average was 90 server fps; the floor was 62. Peak entity count: 107,265. Buildings, deployables and all else included. Memory peak: 2,868 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on [JP]初心者 | momoserver | 10/16 | PVP, and is it online?

Reading: online. [JP]初心者 | momoserver | 10/16 | PVP answers right now. By its reported uptime, the last restart was roughly 12 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

How is [JP]初心者 | momoserver | 10/16 | PVP configured, and what rules are in force?

Reading the name gives no gather rate for [JP]初心者 | momoserver | 10/16 | PVP. The cap on groups is 6 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is [JP]初心者 | momoserver | 10/16 | PVP on?

From seed 663820083, the game generates the procedural map on [JP]初心者 | momoserver | 10/16 | PVP. Its size is 3,850. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto [JP]初心者 | momoserver | 10/16 | PVP?

Press F1 in Rust and enter client.connect 118.27.225.83: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/Myze6ftUv4.

PLACARDS

Server tags

what each one means

Published as mp60,ptrak,$r?,v2635,^b,gmrust,cs168909,ts6

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp60
Max players Slots: 60.
ts6
Group limit Teams are capped at 6.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

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.