Working its way up from the back of the class: #15,246 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 603 places this week.
A term to build on.
Strongest in momentum (D); standing 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
Which region is [JP] Community Rust (仮) | PvE | Monthly based in?
The name of [JP] Community Rust (仮) | PvE | Monthly points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 162.43.90.227:28015.
Is [JP] Community Rust (仮) | PvE | Monthly up, and how steady is its uptime?
You cannot join now: [JP] Community Rust (仮) | PvE | Monthly is offline, last seen 11 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 12 October 2026.
Which Rust version is [JP] Community Rust (仮) | PvE | Monthly running?
Rust network protocol 2634 and build 167584 on Linux is what [JP] Community Rust (仮) | PvE | Monthly runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does [JP] Community Rust (仮) | PvE | Monthly wipe its map?
the force wipe gives the basis for estimating [JP] Community Rust (仮) | PvE | Monthly's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 16 days 6 hours have passed since this world was made. Its tags record that it wipes monthly.
Player numbers
What position does [JP] Community Rust (仮) | PvE | Monthly hold in the rankings?
In the top 70% of all ranked servers, [JP] Community Rust (仮) | PvE | Monthly sits at #15,246 for player hours over the last seven days.
Is [JP] Community Rust (仮) | PvE | Monthly a busy server?
It has been 11 days 7 hours since [JP] Community Rust (仮) | PvE | Monthly was last seen, and it is offline right now.
Tags
What is meant by the tags on [JP] Community Rust (仮) | PvE | Monthly?
The game's browser takes its cue from the tags [JP] Community Rust (仮) | PvE | Monthly has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): This runs on build 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [JP] Community Rust (仮) | PvE | Monthly appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [JP] Community Rust (仮) | PvE | Monthly: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following 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.
Server rules
What settings and rules apply on [JP] Community Rust (仮) | PvE | Monthly?
The name of [JP] Community Rust (仮) | PvE | Monthly gives no gather rate. The group limit stays at the game's default of 8 players. It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
[JP] Community Rust (仮) | PvE | Monthly runs which map?
A procedural map, generated by the game, is what [JP] Community Rust (仮) | PvE | Monthly runs.
Connecting
How do you get onto [JP] Community Rust (仮) | PvE | Monthly?
Enter client.connect 162.43.90.227:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^p,gmrust,cs167584,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167584
BuildThis runs on build 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 momentum (D); standing is the one to work on (F).