RUST METRICSFlight deck · live data
Data live Servers11,857 Players101,834 Populated3,918 Fresh wipes 3 h547 Scan5 min
‹ All servers118.27.230.7:28015
Online Full Queue Fresh wipe Wipe due No query

[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]

Online EA 118.27.230.7:28015 checked 8m ago

3x monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

last reading Thu 18:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

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

Server fps

48 h low 46 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 111,528 ×1000

Entities

48 h range 111,528–119,535 · memory 2,417 MB
1239 ET SINCE RESTART 01:01

Uptime

1 h 1 min since its last restart, at the last reading
7-day average0peak 2
Rank#9,209top 41% · #423 in EA
Last wipe27d agomonthly schedule
Next wipe6d 23hThu 5 Nov, 19:00 UTC FW
Memory2,417MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75120:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608020:0005:0014:0000:0009:0018: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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

usual gap0.3 daysbetween real wipes
wipe-day peak9players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 23hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC34d 23hFW

The first 48 hours of its last wipes

Fri 2 OctFri 2 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 9, 33 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:51 UTC27d ago 9 – running 3
Fri 2 Oct, 00:04 UTC27d ago 9 – 0.3 days 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

Wipe timing

What happens on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] when wipe day comes?

The busiest point of its recent wipes drew 9 players on average. Peak crowd on the latest wipe: 33 hours in.

What wipe timing does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] follow?

The only wipe for [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] is the force wipe, once a month. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 27 days 13 hours ago the current world was made. Its tags carry a monthly wipe schedule.

Tag meanings

How should you read the tags on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

These are the tags [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 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; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EA (East Asia): East Asia is the browser category it sits in. 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] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

These Rust Metrics lists carry [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]: 3x Rust servers, checked live, Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 3x.

Player count

Where does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] sit in the rankings?

Ranked by seven-day player hours, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] sits at #9,209 and #423 in Asia, inside the top 41%.

What player count does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] carry?

Current headcount on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]: 0 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 2. Average at the busiest hour was 1 players, at 10:00 UTC over the last 48 hours.

Server

Which location does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] run from?

[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 118.27.230.7:28015.

What Rust version is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] on?

Rust network protocol 2635 and build 168909 on Linux is the build [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] runs. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

Check: fps. Average 56 server fps over the last 48 hours, low of 46. Within range. Check: entities. The peak was 119,535, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,598 MB. What players call lag comes from low fps and an entity count on the rise.

Is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] up, and how often does it stay up?

Reading: online. [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] answers right now. By its reported uptime, the last restart was roughly 1 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What rules does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] enforce, and what are its settings?

The name carries the rate: 3x gather on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]. 8 players per group, the default value. The mode is pve. Note the following: fighting between players is off. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

From seed 897176852, the game generates the procedural map on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]. Its size is 4,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

What do you do to join [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

To join: start Rust, press F1 and type client.connect 118.27.230.7:28015. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/CUmDuvYpKA is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 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.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Region

EA
East Asia East Asia is the browser category it sits in.

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.