Online EA 118.27.230.7:28015 checked 8m ago
[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]
Connect
srv = rust.server("118.27.230.7:28016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 41% of all ranked servers, top 79% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 1h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 1h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 9, 33 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 06:51 UTC27d ago | 9 | NaN | running | 3 |
| 1 | Fri 2 Oct, 00:04 UTC27d ago | 9 | NaN | 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.
display(srv.map, srv.info())
Map
4000 · seed 897176852
- map
- Procedural Map
- size
- 4000
- seed
- 897176852
Server
srv.info()- address
- 118.27.230.7:28015
- region
- EA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 06:51 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [KR] 쿠키서버 PVE/X3/NPC레이드/낚시/초보 | EA · groups of 8+ · 3x · monthly · 15 on average | 13/100 |
| 1 | 모코코서버 [PVE|X3|이벤트|초보] | EA · groups of 8+ · 3x · monthly · 2 on average | 0/100 |
| 2 | [PVE/X3]병아리서버 초보/힐링/농사/24H | EA · groups of 8+ · 3x · monthly · 1 on average | 2/100 |
| 3 | JP Only|R3SV|PvE|初心者|ミニヘリ|3x|次ワイプ11/06 | EA · groups of 16+ · 3x · monthly · 11 on average | 8/100 |
| 4 | [TW/HK/Asia] EK RUST|月清PVE|2X-2.5X|活動PVP | EA · groups of 16+ · 2x · monthly · 9 on average | 11/50 |
| 5 | Distorted - PVE 3X - Events and Raidable Bases - Biweekly | EA · groups of 8+ · 3x · biweekly · 6 on average | 6/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] rank?
Player hours over the last seven days: #9,215 for [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], #423 in Asia, within the top 41% of the ranked set.
What population does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] carry?
[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Peak hour in the last 48 hours: 10:00 UTC, mean 1 players.
Server data
How well does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] perform?
Averaged over 48 hours: 56 server fps, never under 46. Entity numbers reached 119,535, and that includes buildings, deployables and the rest. The memory field tops out at 3,598 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]. Steam updates your game for you, but the protocol must match to join.
How reliable is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], and is it online now?
[JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] reports itself online at the current refresh. Count back 9 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] hosted?
With its EA tag, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] lists itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 118.27.230.7:28015 is its address.
Rules, settings, map
Which rules apply on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], and what settings?
Gather sits at 3x, read from the server's own name: [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] selected?
The game generates the map on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]: procedural, size 4,000, seed 897176852. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] wipe, and how often?
The only wipe [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] takes is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 27 days 10 hours ago. A monthly wipe schedule is published in its tags.
On [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], what happens on wipe day?
Recent wipes averaged 9 players at their peak. Peak population on the latest wipe came 33 hours in.
Lists and tags
Which lists on Rust Data hold [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], and which filters?
The Rust Data lists that [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] fits are: Modded Rust servers, 3x Rust servers, filtered live and Rust PvE servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
Read by the game's server browser, the tags [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; EA (East Asia): In the server browser it sits under East Asia. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
Enter client.connect 118.27.230.7:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/CUmDuvYpKA.