Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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
from the wipes we sawNot 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| Server | Profile | Players now |
|---|---|---|
| Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 11 / 300 |
| Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 7 / 120 |
| HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP | EA · groups of 8+ · 3x · monthly · 2 on average | 0 / 75 |
| 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3 | EA · groups of 8+ · 3x · 1 on average | 1 / 50 |
| [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 82 on average | 50 / 115 |
| [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 24 on average | 24 / 150 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for Google Cloud Rust JP | 3X | 48H Upkeep: what is it?
With too few of its wipes on record, Google Cloud Rust JP | 3X | 48H Upkeep's rhythm is not yet clear. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was created 69 days 18 hours ago.
Server
What is the hosting location of Google Cloud Rust JP | 3X | 48H Upkeep?
No region tag is published by Google Cloud Rust JP | 3X | 48H Upkeep, but the name points to Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 136.110.109.59:28015 is its address.
Which Rust version is Google Cloud Rust JP | 3X | 48H Upkeep on?
The platform is Linux, with Rust network protocol 2632 and build 161125 running on Google Cloud Rust JP | 3X | 48H Upkeep. Your game must match the protocol to join, and Steam applies that update.
What uptime does Google Cloud Rust JP | 3X | 48H Upkeep show, and is it up?
Offline at this refresh: Google Cloud Rust JP | 3X | 48H Upkeep, last seen 37 days 23 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0%. The first sighting of it by Rust Server Analytics was on 13 September 2026.
Lists and tags
How should the tags on Google Cloud Rust JP | 3X | 48H Upkeep be read?
gmrust (Game mode): Rust survival, standard ruleset; mp20 (Max players): 20 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2632 (Protocol): To join, your game version must match protocol 2632; cs161125 (Build): Build number 161125; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Modded listing, where plugins or settings change the game are the tags Google Cloud Rust JP | 3X | 48H Upkeep publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature Google Cloud Rust JP | 3X | 48H Upkeep?
These Rust Server Analytics lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers: live list and Modded Rust servers: live data. 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.
Player numbers
What position does Google Cloud Rust JP | 3X | 48H Upkeep hold in the server rankings?
Player hours for the last seven days place Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, in the top 70% of the ranked field.
What is the population of Google Cloud Rust JP | 3X | 48H Upkeep?
The last sighting of Google Cloud Rust JP | 3X | 48H Upkeep was 37 days 23 hours ago; it is offline at this refresh.
Map and rules
What settings and rules does Google Cloud Rust JP | 3X | 48H Upkeep use?
Google Cloud Rust JP | 3X | 48H Upkeep names a 3x gather rate. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. VAC, Valve's anti-cheat, is enabled.
The map on Google Cloud Rust JP | 3X | 48H Upkeep: which one is it?
The game generates a procedural map of size 3,500 with seed 1829161776 for Google Cloud Rust JP | 3X | 48H Upkeep. The map is reproducible from its size and seed and can be seen on RustMaps from here.
How to join
What is the way onto Google Cloud Rust JP | 3X | 48H Upkeep?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 136.110.109.59:28015.