Offline 136.110.109.59:28015 checked 37d ago
Google Cloud Rust JP | 3X | 48H Upkeep
Connect
srv = rust.server("136.110.109.59:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
3500 · seed 1829161776
- map
- Procedural Map
- size
- 3500
- seed
- 1829161776
Server
srv.info()- address
- 136.110.109.59:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Aug 2026, 11:29 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 8/300 |
| 1 | Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 4/120 |
| 2 | HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP | EA · groups of 8+ · 3x · monthly · 2 on average | 1/75 |
| 3 | 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3 | EA · groups of 8+ · 3x · 1 on average | 1/50 |
| 4 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 81 on average | 13/115 |
| 5 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 25 on average | 1/150 |
Quick answers
From the figures on this page.
Population data
What position does Google Cloud Rust JP | 3X | 48H Upkeep take in the server rankings?
Player hours over seven days put Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, in the top 70% of the ranked set.
How full does Google Cloud Rust JP | 3X | 48H Upkeep run?
Google Cloud Rust JP | 3X | 48H Upkeep returns no live count at this refresh, having last been seen 37 days 18 hours ago.
Server data
What Rust version does Google Cloud Rust JP | 3X | 48H Upkeep run?
Rust network protocol 2632 and build 161125 on Linux is what Google Cloud Rust JP | 3X | 48H Upkeep runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Google Cloud Rust JP | 3X | 48H Upkeep, and is it up?
The latest sample has Google Cloud Rust JP | 3X | 48H Upkeep offline, with a last sighting 37 days 18 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does Google Cloud Rust JP | 3X | 48H Upkeep run from?
No region tag is published by Google Cloud Rust JP | 3X | 48H Upkeep, though its name points to Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 136.110.109.59:28015.
Rules, settings, map
Which rules apply on Google Cloud Rust JP | 3X | 48H Upkeep, and what settings?
The name carries the figure: Google Cloud Rust JP | 3X | 48H Upkeep runs 3x gather. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on Google Cloud Rust JP | 3X | 48H Upkeep?
Google Cloud Rust JP | 3X | 48H Upkeep runs a procedural map of size 3,500 with seed 1829161776, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does Google Cloud Rust JP | 3X | 48H Upkeep wipe, and on what schedule?
The record for Google Cloud Rust JP | 3X | 48H Upkeep holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 69 days 13 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold Google Cloud Rust JP | 3X | 48H Upkeep, and which filters?
These Rust Data lists include Google Cloud Rust JP | 3X | 48H Upkeep: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
How should you read the server tags on Google Cloud Rust JP | 3X | 48H Upkeep?
Read by the game's server browser, the tags Google Cloud Rust JP | 3X | 48H Upkeep publishes are: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): Slot count: 20; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2632 (Protocol): To join, your game must run protocol 2632; cs161125 (Build): Recorded game build: 161125; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join Google Cloud Rust JP | 3X | 48H Upkeep?
Enter client.connect 136.110.109.59:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.