StatusLive Servers online11,758 Players58,600 Populated3,466 Wiped · 3 h131 Interval5 min Date28 OCT 2026

DWG RG-S1012Server sheetchecked 8m ago

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

Online 118.27.225.83:28015 checked 8m ago

biweekly wipes
Connect
Players now 0/ 60 0% full
7-day average9peak 42
Rank#1,012top 5%
Last wipe12d agobiweekly schedule
Next wipe1d 13hFri 30 Oct, 12:36 UTC
Fig. 1

Players

AveragePeak
0510152023:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Fig. 1Players on [JP]初心者 | momoserver | 10/16 | PVP
Fig. 2

Server performance

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 12:36 UTC, in 1d 13h. 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. 1d 13hFri 30 Oct, 12:36 UTC
  2. 7d 20hThu 5 Nov, 19:00 UTCFW
  3. 15d 13hFri 13 Nov, 12:36 UTC
  4. 29d 13hFri 27 Nov, 12:36 UTC
  5. 35d 20hThu 3 Dec, 19:00 UTCFW
  6. 43d 13hFri 11 Dec, 12:36 UTC

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
020406080+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
『百威』无商城|无权|六人|10.28号14:00清档EA · groups of 6 · biweekly · 13 on average
7 / 100
02
『二次元』|10.26号|新开|六人|新手乐园EA · groups of 6 · weekly · 18 on average
0 / 200
03
[SEA] Rusty IndonesiaEA · groups of 6 · 8 on average
3 / 60
04
【萌新】原倍|10.27档|萌新|纯净|无权EA · groups of 6 · monthly · 2 on average
0 / 100
05
Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 67 on average
11 / 200
06
Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 42 on average
19 / 215
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for [JP]初心者 | momoserver | 10/16 | PVP, and is it up?

[JP]初心者 | momoserver | 10/16 | PVP is up at this moment. The uptime it reports puts the last restart at about 7 hours ago. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is [JP]初心者 | momoserver | 10/16 | PVP stable in the figures recorded?

The last 48 hours give an average of 90 server fps and a floor of 62. Counted at its highest: 107,265 entities, buildings, deployables and the rest of the world included. 2,868 MB is the memory peak. Players feel low fps and a climbing entity count as lag.

What location is recorded for [JP]初心者 | momoserver | 10/16 | PVP?

No region tag is published by [JP]初心者 | momoserver | 10/16 | PVP, but its name points to Asia. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 118.27.225.83:28015 is its address.

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

On Linux, [JP]初心者 | momoserver | 10/16 | PVP runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Counts

How many players are plotted on [JP]初心者 | momoserver | 10/16 | PVP?

0 of 60 slots on [JP]初心者 | momoserver | 10/16 | PVP are taken at the latest refresh. Averaged across seven days, the player count is 9, with a peak of 42. Averaged over the last 48 hours, the player count is highest at 12:00 UTC: 15 players.

In the rankings, which position does [JP]初心者 | momoserver | 10/16 | PVP hold?

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

Wipe times

On [JP]初心者 | momoserver | 10/16 | PVP, what does the data show for wipe day?

The recent wipes averaged a busiest count of 46 players. With 3 more waiting in the queue, the crowd on the latest wipe peaked 27 hours after the wipe. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 9.

On [JP]初心者 | momoserver | 10/16 | PVP, when do wipes occur?

The prediction follows its tag, because too few wipes of [JP]初心者 | momoserver | 10/16 | PVP are on record to confirm the schedule. It is due to wipe next on Friday 30 October at 12:36 UTC. The current world has been in use since 12 days 10 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Rules and settings

Which settings does [JP]初心者 | momoserver | 10/16 | PVP run, and what rules?

Gather rate for [JP]初心者 | momoserver | 10/16 | PVP: not stated in the name. 6 players per group at most. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Community is its tab in the server browser. VAC is on: that is Valve's anti-cheat.

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

[JP]初心者 | momoserver | 10/16 | PVP runs a procedural map of size 3,850 with seed 663820083, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

Where does [JP]初心者 | momoserver | 10/16 | PVP appear among the Rust Graphs lists and filters?

On Rust Graphs, [JP]初心者 | momoserver | 10/16 | PVP is placed in these lists: Rust community servers, plotted. It is returned by these filters on the server list: 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.

Which meaning is attached to each tag on [JP]初心者 | momoserver | 10/16 | PVP?

gmrust (Game mode): Standard survival, as Rust plays; mp60 (Max players): The slot count is 60; ts6 (Group limit): The team limit is 6; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^b (Biweekly): The wipe cycle is two weeks are the tags [JP]初心者 | momoserver | 10/16 | PVP publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Connect

What is the way to connect to [JP]初心者 | momoserver | 10/16 | PVP?

In Rust, press F1 and type client.connect 118.27.225.83:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://discord.com/invite/Myze6ftUv4 is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays.
mp60
Max players The slot count is 60.
ts6
Group limit The team limit is 6.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

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.

KeyTag string decoded