Server profile
Google Cloud Rust JP | 3X | 48H Upkeep
Offline, with 0 of 20 players on; ranked #15,490 of every public Rust server, the top 70%. It last wiped 69d ago.
Offline 136.110.109.59:28015 checked 37d ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 70% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- Japan Tokyo - Limited Raid Hours |3x|PvP|JP9/300
- Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long7/120
- HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP0/75
- 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X30/50
- [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/1026/115
- [SEA] Rust Manila 2x | Biweekly4/150
The short version
Quick answers
From the figures on this page.
Wipe schedule
How often does Google Cloud Rust JP | 3X | 48H Upkeep wipe, and on which day?
Too few wipes are on record for Google Cloud Rust JP | 3X | 48H Upkeep to reveal a rhythm. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. 69 days 16 hours have passed since its current world was created.
Server details
On what version does Google Cloud Rust JP | 3X | 48H Upkeep currently run?
Running on Linux, Google Cloud Rust JP | 3X | 48H Upkeep is on Rust network protocol 2632 and build 161125. Joining needs your game on the same protocol, which Steam updates for you.
Has Google Cloud Rust JP | 3X | 48H Upkeep stayed online, and is it up now?
Offline at the moment, Google Cloud Rust JP | 3X | 48H Upkeep was last seen 37 days 22 hours ago. The last 7 full days gave 0 of 168 hours up, or 0% of the time. The first record Rust Insights has of it is 13 September 2026.
What location is listed for Google Cloud Rust JP | 3X | 48H Upkeep?
The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, even though no region tag is published. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. You can reach it at 136.110.109.59:28015.
Lists and tags
How should you read the tags listed for Google Cloud Rust JP | 3X | 48H Upkeep?
The tags gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): It holds 20 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2632 (Protocol): To join you need the same version; protocol 2632; cs161125 (Build): Build 161125 is what it runs; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, placing it under Modded are what Google Cloud Rust JP | 3X | 48H Upkeep publishes, and the server browser in the game reads them. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.
Where does Google Cloud Rust JP | 3X | 48H Upkeep turn up among the Rust Insights lists and filters?
These Rust Insights lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers, filtered live and Modded Rust servers, explained. 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 counts
How many players are on Google Cloud Rust JP | 3X | 48H Upkeep right now, and how does that number move?
Google Cloud Rust JP | 3X | 48H Upkeep was last seen 37 days 22 hours ago and is offline right now.
Where does Google Cloud Rust JP | 3X | 48H Upkeep sit in the rankings?
The player-hours ranking for the last seven days puts Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, among the top 70% of all ranked servers.
Settings and rules
What settings and rules apply on Google Cloud Rust JP | 3X | 48H Upkeep?
A 3x gather rate is what the name of Google Cloud Rust JP | 3X | 48H Upkeep states. Groups can reach 8 players, which is the default in the game. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Oxide of them. VAC is on: Valve's anti-cheat is active.
Which map is live on Google Cloud Rust JP | 3X | 48H Upkeep?
The game generates the map on Google Cloud Rust JP | 3X | 48H Upkeep: procedural, size 3,500, seed 1829161776. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.
How to join
How do you connect to Google Cloud Rust JP | 3X | 48H Upkeep?
Type client.connect 136.110.109.59:28015 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam.