Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestTop 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
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
the same kind of game, then region, group limit, rate and wipes- 5/300
- 6/120
- 0/75
- 2/50
- 36/115
- 2/150
Quick answers
from the figures on this pageWipe timing
What wipe timing does Google Cloud Rust JP | 3X | 48H Upkeep follow?
Its rhythm cannot be told from the wipes of Google Cloud Rust JP | 3X | 48H Upkeep on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 69 days 10 hours ago the current world was made.
Lists and filters
How should you read the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
Tags published by Google Cloud Rust JP | 3X | 48H Upkeep, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): Slots: 20; ts8 (Group limit): Default limit in force: 8 per team; v2632 (Protocol): Protocol 2632: join only on the same game version; cs161125 (Build): The server runs game build 161125; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Google Cloud Rust JP | 3X | 48H Upkeep appear in Rust Metrics lists and filters?
On Rust Metrics, Google Cloud Rust JP | 3X | 48H Upkeep sits in these lists: 3x Rust servers, checked live and Modded Rust servers, checked live. 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; Gather rate: 3x.
Population
Where does Google Cloud Rust JP | 3X | 48H Upkeep sit in the rankings?
Player hours over seven days put Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, in the top 70% of all ranked servers.
What player count does Google Cloud Rust JP | 3X | 48H Upkeep carry?
Status for Google Cloud Rust JP | 3X | 48H Upkeep: offline. Last seen 37 days 16 hours ago.
Operator and location
Where does Google Cloud Rust JP | 3X | 48H Upkeep sit?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, though it publishes no region tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 136.110.109.59:28015.
What Rust version is Google Cloud Rust JP | 3X | 48H Upkeep on?
Rust network protocol 2632 and build 161125 on Linux is the build Google Cloud Rust JP | 3X | 48H Upkeep runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Google Cloud Rust JP | 3X | 48H Upkeep, and is it online?
Reading: offline. Google Cloud Rust JP | 3X | 48H Upkeep last answered 37 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does Google Cloud Rust JP | 3X | 48H Upkeep enforce, and what are its settings?
The name carries the rate: 3x gather on Google Cloud Rust JP | 3X | 48H Upkeep. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
What map is Google Cloud Rust JP | 3X | 48H Upkeep on?
Size 3,500 and seed 1829161776: the game generates the procedural map on Google Cloud Rust JP | 3X | 48H Upkeep from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
How do you connect to Google Cloud Rust JP | 3X | 48H Upkeep?
Press F1 in Rust and enter client.connect 136.110.109.59:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.