On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,269top 68%
Last wipe55d agono schedule published
Next wipe–no wipe seen yet
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
32/ 100
F
Working its way up from the back of the class: #15,269 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
97/ 100
A+
Runs smoothly: 58 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
50/ 100
D
Holding steady: down 144 places this week.
A fair term, with more to come.
Strongest in performance (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 68% 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
The name of [JP][PVE]UC-RUST-Server points to Asia, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 118.27.225.39:28015.
How reliable is [JP][PVE]UC-RUST-Server, and is it up?
The server is up: [JP][PVE]UC-RUST-Server is online now. The uptime it reports puts the last restart at about 22 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [JP][PVE]UC-RUST-Server run?
The average over the last 48 hours was 58 server fps, and it never went below 44. At its peak, it held 106,934 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,090 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is [JP][PVE]UC-RUST-Server running?
You will find [JP][PVE]UC-RUST-Server on Rust network protocol 2633 and build 162929, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does [JP][PVE]UC-RUST-Server reset?
There are too few wipes on record for [JP][PVE]UC-RUST-Server to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 55 days 20 hours.
Population
Where does [JP][PVE]UC-RUST-Server place in the wider field of Rust servers?
In the top 68% of all ranked servers, [JP][PVE]UC-RUST-Server sits at #15,269 for player hours over the last seven days.
Is [JP][PVE]UC-RUST-Server a busy server?
Right now, 0 players are on [JP][PVE]UC-RUST-Server, which has 50 slots. A seven-day average of 0 players applies here.
Tags
What do [JP][PVE]UC-RUST-Server's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags [JP][PVE]UC-RUST-Server publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [JP][PVE]UC-RUST-Server?
Rust Server Score lists that include [JP][PVE]UC-RUST-Server: Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is [JP][PVE]UC-RUST-Server set up, and what rules does it keep?
Nothing in the name of [JP][PVE]UC-RUST-Server states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [JP][PVE]UC-RUST-Server?
The game generates the procedural map on [JP][PVE]UC-RUST-Server at size 4,000 with seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
How to join
How should you connect to [JP][PVE]UC-RUST-Server?
To connect, start Rust, press F1, and type client.connect 118.27.225.39:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildBuild number: 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).