Google Cloud Rust JP | 3X | 48H Upkeep
136.110.109.59:28015 checked 22d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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
Quick answers
Player Numbers
Where does Google Cloud Rust JP | 3X | 48H Upkeep sit in the rankings?
Over the last seven days, Google Cloud Rust JP | 3X | 48H Upkeep ranks #15,490 in player hours, which is in the top 70% of ranked servers.
What is the player count on Google Cloud Rust JP | 3X | 48H Upkeep?
The server Google Cloud Rust JP | 3X | 48H Upkeep is currently offline; it was last seen 22 days 18 hours ago.
Tags & Lists
What is the meaning of the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
For Google Cloud Rust JP | 3X | 48H Upkeep, the game's server browser reads the following tags: gmrust (Game mode): Rust survival, standard; mp20 (Max players): Slot count is 20; ts8 (Group limit): Teams are limited to 8, the default; v2632 (Protocol): Protocol 2632: join only if your game matches this version; cs161125 (Build): Build 161125; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code missing; ^o (Oxide): Uses Oxide (uMod) for plugins; ^z (Modded): Under Modded, because plugins or settings modify play. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Where does Google Cloud Rust JP | 3X | 48H Upkeep appear in BestRustServers.xyz lists and filters?
These BestRustServers.xyz lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers by live players and Best modded Rust servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Server Overview
What Rust version is Google Cloud Rust JP | 3X | 48H Upkeep on?
The combination is Rust network protocol 2632 and build 161125 on Linux for Google Cloud Rust JP | 3X | 48H Upkeep. Your game has to match the protocol to connect; Steam takes care of updating it.
What is the uptime and reliability of Google Cloud Rust JP | 3X | 48H Upkeep?
Last seen 22 days 18 hours ago, Google Cloud Rust JP | 3X | 48H Upkeep is currently offline. Over the past 7 full days, it was online 0 of 168 hours, 0% of the time. It was first seen by BestRustServers.xyz on 13 September 2026.
Where can Google Cloud Rust JP | 3X | 48H Upkeep be found?
Its name points to Asia, though Google Cloud Rust JP | 3X | 48H Upkeep publishes no region tag. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. 136.110.109.59:28015 is its address.
Settings & Map
Google Cloud Rust JP | 3X | 48H Upkeep map: which one is it?
On Google Cloud Rust JP | 3X | 48H Upkeep, the map is procedural, size 3,500 with seed 1829161776, generated by the game. View it on RustMaps from this page: identical size and seed produce an identical map.
Google Cloud Rust JP | 3X | 48H Upkeep rules and settings: what are they?
3x gather: that is the rate Google Cloud Rust JP | 3X | 48H Upkeep states in its name. The default cap of 8 players per group is in force. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. The Modded section of the browser holds it: plugins or settings apply. Plugins in use: Oxide. The server has VAC on.
Wipe Schedule
Google Cloud Rust JP | 3X | 48H Upkeep wipe schedule: what does it show?
Too few wipes are on record for Google Cloud Rust JP | 3X | 48H Upkeep to reveal its rhythm. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. The world in play was made 54 days 13 hours.
Connect
How can I connect to Google Cloud Rust JP | 3X | 48H Upkeep?
Use the F1 console: client.connect 136.110.109.59:28015. Launch Rust on this page does the same by opening Rust through Steam and connecting.
Server tags
Published as mp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust- Game mode Rust survival, standard.
mp20- Max players Slot count is 20.
ts8- Group limit Teams are limited to 8, the default.
v2632- Protocol Protocol 2632: join only if your game matches this version.
cs161125- Build Build 161125.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code missing.
Mods and access
^o- Oxide Uses Oxide (uMod) for plugins.
^z- Modded Under Modded, because plugins or settings modify play.
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.