An entry in the registerNo. 15,490
Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
Google Cloud Rust JP | 3X | 48H Upkeep is a Rust server. It was offline at the last count. It stands at No. 15,490 of the ranked servers, the top 70%. It last wiped 69d ago. Its own tags class it as 3x, modded, oxide.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
§ 4The wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
§ 5The record of wipesnewest 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.
§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 Japan Tokyo - Limited Raid Hours |3x|PvP|JP6/300 EA · groups of 8+ · 3x · weekly · 40 on average
- 2 Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long1/120 EA · groups of 100+ · 3x · monthly · 7 on average
- 3 HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP0/75 EA · groups of 8+ · 3x · monthly · 2 on average
- 4 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X33/50 EA · groups of 8+ · 3x · 1 on average
- 5 [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/1046/115 EA · groups of 8+ · 2x · biweekly · 81 on average
- 6 [SEA] Rust Manila 2x | Biweekly3/150 EA · groups of 8+ · 2x · biweekly · 25 on average
§ 7Questions answeredfrom the figures in this entry
Server record
On which Rust version does Google Cloud Rust JP | 3X | 48H Upkeep operate?
Rust network protocol 2632 and build 161125 on Linux is what Google Cloud Rust JP | 3X | 48H Upkeep runs. To join, your game must be on the same protocol; Steam handles the update.
What does uptime look like on Google Cloud Rust JP | 3X | 48H Upkeep, and is it up?
Offline at present: Google Cloud Rust JP | 3X | 48H Upkeep, last seen 37 days 15 hours ago. The records show 0% uptime over the last 7 full days: 0 of 168 hours up. The first sighting at Rust Server Stats was on 13 September 2026.
What is the location of Google Cloud Rust JP | 3X | 48H Upkeep?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, though no region tag is published. The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. At 136.110.109.59:28015 stands the address.
Settings and map
What map does Google Cloud Rust JP | 3X | 48H Upkeep put players on?
Google Cloud Rust JP | 3X | 48H Upkeep runs a procedural map, generated by the game, of size 3,500 with seed 1829161776. RustMaps can display it from this page, since equal size and seed yield the same map.
The rules and settings of Google Cloud Rust JP | 3X | 48H Upkeep: what are they?
Google Cloud Rust JP | 3X | 48H Upkeep carries a gather rate of 3x in its title. Eight players per group is the default and the limit here. Play is survival, gather, build and raid: the standard game. Player-versus-player fighting and raiding are enabled. Plugins or settings change the game; it appears under Modded in the browser. The plugin set is Oxide. The VAC anti-cheat from Valve is active.
Player record
What are the player numbers on Google Cloud Rust JP | 3X | 48H Upkeep?
Google Cloud Rust JP | 3X | 48H Upkeep is offline at present; the last response came 37 days 15 hours ago.
Against other Rust servers, how is Google Cloud Rust JP | 3X | 48H Upkeep ranked?
The seven-day player-hour table places Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, within the top 70% of ranked servers.
Tags, lists
Google Cloud Rust JP | 3X | 48H Upkeep sits in which Rust Server Stats lists and filters?
The Rust Server Stats lists Google Cloud Rust JP | 3X | 48H Upkeep fits: 3x Rust servers: the record and Modded Rust servers. On the server list it comes up under these filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
Which meanings attach to the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
These tags are Google Cloud Rust JP | 3X | 48H Upkeep's, and the game's browser reads them: gmrust (Game mode): Standard survival, as Rust plays it; mp20 (Max players): 20 is the number of slots; ts8 (Group limit): 8 to a team, which is the default; v2632 (Protocol): The game version must match protocol 2632 to join; cs161125 (Build): Build 161125; ptrak (Networking): RakNet carries it, the standard layer for the game; $r? (Region code): The region code is not set; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): Under Modded, because settings or plugins alter the game. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.
The wipes
When does Google Cloud Rust JP | 3X | 48H Upkeep wipe?
Too few wipes of Google Cloud Rust JP | 3X | 48H Upkeep are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe takes every Rust server, without exception. The world now in play was generated 69 days 9 hours ago.
How to join
How does one connect to Google Cloud Rust JP | 3X | 48H Upkeep?
Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 136.110.109.59:28015.