Working its way up from the back of the class: #15,490 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
51/ 100
D
Moving up: up 360 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.
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 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
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
In what location does Google Cloud Rust JP | 3X | 48H Upkeep sit?
The name of Google Cloud Rust JP | 3X | 48H Upkeep 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. 136.110.109.59:28015 is the address to use.
How dependable is Google Cloud Rust JP | 3X | 48H Upkeep, and is it online at the moment?
You cannot join now: Google Cloud Rust JP | 3X | 48H Upkeep is offline, last seen 37 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is Google Cloud Rust JP | 3X | 48H Upkeep running?
Rust network protocol 2632 and build 161125 on Linux is what Google Cloud Rust JP | 3X | 48H Upkeep runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Google Cloud Rust JP | 3X | 48H Upkeep reset?
There are too few wipes on record for Google Cloud Rust JP | 3X | 48H Upkeep 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. It has been running its current world for 69 days 12 hours.
Population
Where does Google Cloud Rust JP | 3X | 48H Upkeep sit among Rust servers?
In the top 70% of all ranked servers, Google Cloud Rust JP | 3X | 48H Upkeep sits at #15,490 for player hours over the last seven days.
Is Google Cloud Rust JP | 3X | 48H Upkeep a busy server?
It has been 37 days 17 hours since Google Cloud Rust JP | 3X | 48H Upkeep was last seen, and it is offline right now.
Tags and filters
What do Google Cloud Rust JP | 3X | 48H Upkeep's tags stand for?
You'll see Google Cloud Rust JP | 3X | 48H Upkeep tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs161125 (Build): Build number: 161125; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 lists and filters on Rust Server Score show Google Cloud Rust JP | 3X | 48H Upkeep?
Rust Server Score lists that include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Map and rules
How is Google Cloud Rust JP | 3X | 48H Upkeep set up, and what rules does it keep?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to a 3x gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Google Cloud Rust JP | 3X | 48H Upkeep?
Google Cloud Rust JP | 3X | 48H Upkeep runs a game-generated procedural map at size 3,500, seed 1829161776. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join Google Cloud Rust JP | 3X | 48H Upkeep?
To connect, start Rust, press F1, and type client.connect 136.110.109.59:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersIts slot count is 20.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs161125
BuildBuild number: 161125.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).