On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#9,876top 44% · #435 in EA
Last wipe27d agomonthly schedule
Next wipe7d 7hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
56/ 100
C−
Working its way up from the back of the class: #9,876 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
92/ 100
A
Mostly smooth: 55 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
22/ 100
F
Lost ground: down 5,579 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 44% of all ranked servers, top 79% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h.
The force wipe · high confidence
usual gap0.3 daysbetween real wipes
wipe-day peak9players, last three wipes
Coming wipes
7d 7hThu 5 Nov, 19:00 UTCFW
35d 7hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Fri 2 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 9, 33 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
You'll see [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] listed in Asia, tagged EA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 118.27.230.7:28015 is the address to use.
How dependable is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard], and is it online at the moment?
You can join now: [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] is online. The uptime it reports puts the last restart at about 4 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] perform well?
It never fell below 46 server fps in the last 48 hours, averaging 55. Up to 121,487 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 3,598 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] on?
You will find [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] wipe its map?
Once a month, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] wipes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 27 days 5 hours. Its tags record that it wipes monthly.
What should you expect from wipe day on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
Recent wipes have peaked at 9 players on average. 33 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] sit among Rust servers?
Over the last seven days, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] has #9,876 for player hours, in the top 44% of all ranked servers and #435 in Asia.
Is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] a busy server?
With 50 slots available, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] currently has 0 players. The seven-day average is 0 players, with a peak of 2. The busiest time in the last 48 hours was 10:00 UTC, with an average of 1 players.
Tags
How should you read the tags on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
The game's browser takes its cue from the tags [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): In the server browser it appears under East Asia. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
These Rust Server Score lists count [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] among them: 3x Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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.
Map and rules
How is [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] set up, and what rules does it keep?
Going by its name, [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] runs 3x gather. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
The game generates the procedural map on [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard] at size 4,000 with seed 897176852. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How do you get onto [JP] [PVE] COCORU 3X server [MOD 120+] [Easy or Hard]?
To connect, start Rust, press F1, and type client.connect 118.27.230.7:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/CUmDuvYpKA.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^m,EA,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaIn the server browser it appears 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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).