Skip to the page
RUST ANALYTICS
LIVE43,380PLY11,503SRV
QUOTE 118.27.230.7:28015 Online EA checked 11m ago

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

3x monthly wipes moddedoxidepve
Players · last
1/ 50
−1−50.0%24h
2% full
Day range 0 7
7-day avg 2 peak 7
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
1/ 50
2% full
Change · 24h
−1
−50.0% from 2
7-day average
2
peak 7
Rank
#2,622
top 12% · #254 in EA
Rank · 7d ago
#2,564
58 places down
Last wipe
13d ago
monthly schedule
Next wipe
21d 9h
Thu 5 Nov, 19:00 UTC FW
Group limit
8
8, the default
Gather rate
3x
read from the name
Score
268
player hours, last seven days
Map
4000
Procedural Map · seed 897176852
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
0246810:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC. Busiest hour of the two days: 7 players.

Server performance

02040608010:0019:0004:0014:0023:0008: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
11k2k3k4k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

Wipe schedule

force wipes only
Next wipeThursday 5 November, 19:00 UTCin 21d 9h

The force wipe · high confidence

usual gap
0.3 days
between real wipes
wipe-day peak
9
players, last three wipes

Coming wipes

  1. 21d 9hThu 5 Nov, 19:00 UTCFW

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.

Wipes

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

Similar servers

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1[KR] 쿠키서버 PVE/X3/NPC레이드/낚시/초보EA · groups of 8+ · 3x · monthly · 28 on average27/100+0+0.3%
2모코코서버 [PVE|X3|이벤트|초보]EA · groups of 8+ · 3x · monthly · 2 on average0/100−1−100.0%
3[TW/HK/Asia] EK RUST|月清PVE|2X-2.5X|活動PVPEA · groups of 16+ · 2x · monthly · 10 on average9/50−2−18.8%
4SEA | Eclipse | PVE 5x | Newbie Friendly | Events | Perfectly MEA · groups of 8+ · 5x · monthly · 7 on average5/100−2−30.2%
5Distorted - PVE 3X - Events and Raidable Bases - BiweeklyEA · groups of 8+ · 3x · biweekly · 5 on average4/200+1+37.1%
6RnC PVE 3X | Wiped: 01/10 EA · groups of 30+ · 3x · biweekly · 3 on average1/50−2−62.5%

Quick answers

from the figures on this page

Server Rules

How is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] configured in terms of rules and settings?

A gather rate of 3x appears in the name of [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]. Groups can contain a maximum of 8 players, the default for the game. pve is the mode, player-versus-player combat is absent. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. VAC is active.

What is the current map on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

The map on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] is procedural, size 4,000, with seed 897176852, and generated by the game. You can see the map on RustMaps from this page, as the same size and seed give the same map.

Player Count

What position does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] hold in the server rankings?

On seven-day player hours, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] sits at #2,622, in the top 12% across ranked servers and #254 in Asia.

How many players does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] have?

On [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], 1 players are in now, out of 50 slots. The seven-day average is 2 players, with a peak of 7. The busiest hour in the last 48 hours was 13:00 UTC, with an average of 6 players.

Wipe Schedule

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

Recent wipes at this server drew an average peak of 9 players. On the latest wipe, 33 hours after the wipe, the crowd peaked.

When does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] schedule its wipes?

The only wipe at [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] 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 at that time. This world has been running for 13 days 2 hours. The tags state monthly wipes.

Server Info

What is the location of [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

In Asia, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] lists itself with the EA tag. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 118.27.230.7:28015.

Is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] performing well?

Server fps over the last 48 hours: 26 on average, 4 at the lowest. The entity count reached 133,364, covering buildings, deployables and all else in the world. The memory ceiling reached 4,430 MB. A climbing entity count plus low fps is the lag players report.

[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] runs which version of Rust?

The version in use at [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]: Rust network protocol 2634 and build 166494, on Linux. Your game needs the same protocol to get in; Steam takes care of the update.

Is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] up, and how consistent is its uptime?

The server is live: [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] is online. The reported uptime puts its last restart at about 3 hours ago. 7 full days have passed with 100% uptime, 168 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.

Tags & Filters

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

Published by [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] for the game's server browser to read: gmrust (Game mode): Rust's standard survival mode; mp50 (Max players): Slot count: 50; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166494 (Build): It runs build 166494; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^m (Monthly): Facepunch's force wipe sets the schedule: one wipe a month; ^p (PvE): Player-versus-player fighting is off; the world supplies the danger; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; EA (East Asia): The server browser files it under East Asia. The top of this page and the tags both show its players now, its queue and when its world was made.

Where does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] show up in Rust Analytics lists and filters?

On Rust Analytics, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] matches these lists: 3x Rust servers, Modded Rust servers and Best Rust PvE servers. It appears under these filters on the server list: 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; Last wipe: In the last 2 weeks; Gather rate: 3x.

Joining the Server

What is the process to join [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?

The console route: start Rust, press F1, enter client.connect 118.27.230.7:28015. The page's Launch Rust button opens Rust through Steam and connects you instead. For more information, go to https://discord.com/invite/CUmDuvYpKA.

Server tags

what each one means

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

Game

gmrust
Game mode Rust's standard survival mode.
mp50
Max players Slot count: 50.
ts8
Group limit At the game default, teams hold up to 8.
v2634
Protocol Your game must run protocol 2634 to connect.
cs166494
Build It runs build 166494.
ptrak
Networking Runs on RakNet, Rust's default network layer.
$r?
Region code The region code is absent.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the schedule: one wipe a month.

Gameplay

^p
PvE Player-versus-player fighting is off; the world supplies the danger.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

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.