Local forecast
Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
Current conditions
observed 37d agoplayers now
0% full
- 7-day average
- 0
- peak –
- Rank
- #15,490
- top 70%
- Last wipe
- 69d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
Next wipe
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
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.
Past weather: its 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer facts
Is Google Cloud Rust JP | 3X | 48H Upkeep online at the moment, and how consistent is its uptime?
Google Cloud Rust JP | 3X | 48H Upkeep is currently offline, with the last sighting 37 days 16 hours ago. It was up for 0 of 168 hours across the last 7 full days, 0% of the time. The first sighting by Rust Wipe Stats was on 13 September 2026.
In which location does Google Cloud Rust JP | 3X | 48H Upkeep sit?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, but no region tag is published. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 136.110.109.59:28015 is its address.
What version of Rust is running on Google Cloud Rust JP | 3X | 48H Upkeep?
On Google Cloud Rust JP | 3X | 48H Upkeep you will find Rust network protocol 2632 and build 161125, hosted on Linux. To join you need the same protocol, and Steam handles the update.
Tags, lists and filters
Which meaning sits behind each tag on Google Cloud Rust JP | 3X | 48H Upkeep?
The server browser reads these tags from Google Cloud Rust JP | 3X | 48H Upkeep: gmrust (Game mode): The mode is plain Rust survival; mp20 (Max players): It holds 20 players; ts8 (Group limit): This is the standard limit: 8 to a team; v2632 (Protocol): Your game must run protocol 2632 to get in; cs161125 (Build): Game build: 161125; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): This server carries no region code; ^o (Oxide): Oxide, known too as uMod, provides the plugin framework; ^z (Modded): Plugins or settings alter the game here, so it is listed under Modded. The tags hold the current players, the queue length and the world's creation time, and these appear at the top of this page.
Where does Google Cloud Rust JP | 3X | 48H Upkeep appear among the Rust Wipe Stats lists and filters?
These Rust Wipe Stats lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers and Modded Rust servers. These filters on the server list will bring it up: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Settings and rules
Which map is in use on Google Cloud Rust JP | 3X | 48H Upkeep?
Google Cloud Rust JP | 3X | 48H Upkeep runs a procedural map of size 3,500, seed 1829161776, made by the game. From this page RustMaps opens it, since equal size and seed give an equal map.
Which settings and rules are in force on Google Cloud Rust JP | 3X | 48H Upkeep?
Its name carries the gather figure: 3x on Google Cloud Rust JP | 3X | 48H Upkeep. Groups fall back to the game's default of 8 players. This server runs survival, the usual game of gathering, building and raiding. Raiding and player combat are both allowed. The server browser lists it as Modded, where plugins or settings alter the game. It runs these plugin frameworks: Oxide. This server has VAC switched on.
Wipe schedule
On what schedule does Google Cloud Rust JP | 3X | 48H Upkeep wipe?
Its rhythm cannot be read yet, as too few of Google Cloud Rust JP | 3X | 48H Upkeep's wipes are on record. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. 69 days 11 hours is how long the current world has been running.
Player counts
How many players does Google Cloud Rust JP | 3X | 48H Upkeep hold?
The last time Google Cloud Rust JP | 3X | 48H Upkeep was seen was 37 days 16 hours ago; it is offline right now.
How does Google Cloud Rust JP | 3X | 48H Upkeep compare with other Rust servers in the rankings?
Ranked #15,490 on seven-day player hours, Google Cloud Rust JP | 3X | 48H Upkeep is in the top 70% of all ranked servers.
Getting in
What steps let you join Google Cloud Rust JP | 3X | 48H Upkeep?
Enter client.connect 136.110.109.59:28015 in the Rust console, which F1 opens. Or join via Launch Rust on this page, opening Rust through Steam and connecting you.