StatusLive Servers online11,776 Players67,745 Populated3,535 Wiped · 3 h197 Interval5 min Date29 OCT 2026

DWG RG-S2063Server sheetchecked 12m ago

모코코서버 [PVE|X3|이벤트|초보]

Online EA 219.248.160.167:28025 checked 12m ago

3x monthly wipes moddedcarbonpve
Connect
Players now 1/ 100 1% full
7-day average2peak 10
Rank#2,063top 9% · #195 in EA
Last wipe27d agomonthly schedule
Next wipe7d 6hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0123413:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

Fig. 1Players on 모코코서버 [PVE|X3|이벤트|초보]
Fig. 2

Server performance

02040608013:0022:0007:0016:0002:0011: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
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

force wipes only

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

wipe-day peak7players, last three wipes

Coming wipes

  1. 7d 6hThu 5 Nov, 19:00 UTCFW
  2. 35d 6hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

02468+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 7, 29 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 23:49 UTC FW27d ago 7 – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[KR] 쿠키서버 PVE/X3/NPC레이드/낚시/초보EA · groups of 8+ · 3x · monthly · 15 on average
27 / 100
02
[PVE/X3]병아리서버 초보/힐링/농사/24HEA · groups of 8+ · 3x · monthly · 1 on average
1 / 100
03
JP Only|R3SV|PvE|初心者|ミニヘリ|3x|次ワイプ11/06EA · groups of 16+ · 3x · monthly · 11 on average
25 / 100
04
[TW/HK/Asia] EK RUST|月清PVE|2X-2.5X|活動PVPEA · groups of 16+ · 2x · monthly · 10 on average
17 / 50
05
Distorted - PVE 3X - Events and Raidable Bases - BiweeklyEA · groups of 8+ · 3x · biweekly · 6 on average
8 / 200
06
SEA | Eclipse | PVE 5x | Newbie Friendly | Events | Perfectly MEA · groups of 8+ · 5x · monthly · 4 on average
7 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for 모코코서버 [PVE|X3|이벤트|초보], and is it up?

모코코서버 [PVE|X3|이벤트|초보] is up at this moment. Counted from its reported uptime, the last restart was about 15 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 13 September 2026.

Is 모코코서버 [PVE|X3|이벤트|초보] stable in the figures recorded?

Average server fps over the last 48 hours is 59; the lowest was 54. Counted at its highest: 183,444 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 7,116 MB. Players feel low fps and a climbing entity count as lag.

What location is recorded for 모코코서버 [PVE|X3|이벤트|초보]?

In Asia 모코코서버 [PVE|X3|이벤트|초보] lists itself, tagged EA. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 219.248.160.167:28025.

On which Rust version is 모코코서버 [PVE|X3|이벤트|초보] running?

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on 모코코서버 [PVE|X3|이벤트|초보]. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on 모코코서버 [PVE|X3|이벤트|초보]?

1 of 100 slots on 모코코서버 [PVE|X3|이벤트|초보] are taken at the latest refresh. Averaged across seven days, the player count is 2, with a peak of 10. Over the last 48 hours the busiest hour was 14:00 UTC, at an average of 3 players.

What rank has been recorded for 모코코서버 [PVE|X3|이벤트|초보]?

The same seven-day player-hour count places 모코코서버 [PVE|X3|이벤트|초보] at #195 within Asia, #2,063 across all ranked servers and in the top 9% of them.

Wipe data

What is recorded on 모코코서버 [PVE|X3|이벤트|초보] on wipe day?

An average of 7 players was recorded at the busiest point of its recent wipes. 29 hours after the latest wipe, the crowd peaked.

What wipe schedule has been recorded for 모코코서버 [PVE|X3|이벤트|초보]?

At 모코코서버 [PVE|X3|이벤트|초보] the only wipe is the monthly force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 27 days 12 hours ago. A wipe every month is the schedule its tags set out.

Settings

Which rules and settings are recorded for 모코코서버 [PVE|X3|이벤트|초보]?

3x gather is stated in the name of 모코코서버 [PVE|X3|이벤트|초보]. No limit is published beyond the default: 8 players per group. pve, no fighting other players, is the game mode. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Carbon. Anti-cheat: VAC, from Valve, is on.

On which map is 모코코서버 [PVE|X3|이벤트|초보] played?

Size 5,000 with seed 346176: that is the procedural map 모코코서버 [PVE|X3|이벤트|초보] runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

Where does 모코코서버 [PVE|X3|이벤트|초보] appear among the Rust Graphs lists and filters?

These Rust Graphs lists include 모코코서버 [PVE|X3|이벤트|초보]: 3x Rust servers, plotted, Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 3x.

Which meaning is attached to each tag on 모코코서버 [PVE|X3|이벤트|초보]?

The game's server browser reads these tags from 모코코서버 [PVE|X3|이벤트|초보]: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^p (PvE): Player fights are off; the world supplies the danger; ^z (Modded): Plugins or settings change the game, so it is listed under Modded; ^y (Carbon): The plugin framework is Carbon; EA (East Asia): The server browser lists it under East Asia. 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 모코코서버 [PVE|X3|이벤트|초보]?

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

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Wipe schedule

^m
Monthly Facepunch's force wipe brings a monthly wipe.

Gameplay

^p
PvE Player fights are off; the world supplies the danger.

Mods and access

^z
Modded Plugins or settings change the game, so it is listed under Modded.
^y
Carbon The plugin framework is Carbon.

Region

EA
East Asia The server browser lists 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.

KeyTag string decoded