Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
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.
Wipes
every wipe as a delivery, newest first- 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.
- Japan Tokyo - Limited Raid Hours |3x|PvP|JP 14 / 300
- Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long 9 / 120
- HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP 0 / 75
- 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3 1 / 50
- SIX-SEVEN 67 | Max 8 | SEA | Kits | Shop | 3X | Wiped 10/28 16 / 150
- [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 174 / 205
Quick answers
From the figures on this page.
Player activity
Where does Google Cloud Rust JP | 3X | 48H Upkeep place among Rust servers?
A seven-day player-hours count places Google Cloud Rust JP | 3X | 48H Upkeep at #15,490: the top 70% of every ranked server.
Is Google Cloud Rust JP | 3X | 48H Upkeep busy at the moment?
The last sighting of Google Cloud Rust JP | 3X | 48H Upkeep was 37 days 13 hours ago; it is offline right now.
Map and rules
On what map does Google Cloud Rust JP | 3X | 48H Upkeep take place?
Size 3,500 and seed 1829161776 define the procedural map Google Cloud Rust JP | 3X | 48H Upkeep runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.
Which settings and rules apply on Google Cloud Rust JP | 3X | 48H Upkeep?
The name of Google Cloud Rust JP | 3X | 48H Upkeep announces 3x gathering. Up to 8 players can join a group, the default for the game. survival is the mode, the usual game: build, gather, raid. You can raid and fight other players. Because plugins or settings change the game, it is filed under Modded in the server browser. Plugins come from Oxide. VAC, the anti-cheat from Valve, is active.
Server details
What location does Google Cloud Rust JP | 3X | 48H Upkeep run from?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, though no region tag is published. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. The address to connect to is 136.110.109.59:28015.
How reliable is Google Cloud Rust JP | 3X | 48H Upkeep, and is it currently online?
The current status for Google Cloud Rust JP | 3X | 48H Upkeep is offline, last seen 37 days 13 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. 13 September 2026 is when Rust Wipe Tracker first recorded it.
What Rust version is Google Cloud Rust JP | 3X | 48H Upkeep using?
The version on Google Cloud Rust JP | 3X | 48H Upkeep is Rust network protocol 2632 and build 161125, running on Linux. To join, your game must be on the same protocol; Steam handles that update for you.
Map resets
How often does Google Cloud Rust JP | 3X | 48H Upkeep wipe, and at what times?
To tell its rhythm we would need more of Google Cloud Rust JP | 3X | 48H Upkeep's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. The world it is running was made 69 days 8 hours.
Tags and listings
Where does Google Cloud Rust JP | 3X | 48H Upkeep appear across the Rust Wipe Tracker lists and filters?
You will find Google Cloud Rust JP | 3X | 48H Upkeep on the following Rust Wipe Tracker lists: 3x Rust servers and Modded Rust servers. These are the filters that 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.
How should you read the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
The game's server browser picks up these Google Cloud Rust JP | 3X | 48H Upkeep tags: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): It holds 20 slots; ts8 (Group limit): 8 per team, which is the default; v2632 (Protocol): To join, your game must match protocol 2632; cs161125 (Build): Build number: 161125; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
Connecting
How do you connect to Google Cloud Rust JP | 3X | 48H Upkeep?
Enter client.connect 136.110.109.59:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.