Live coverage · Rust server
Offline Google Cloud Rust JP | 3X | 48H Upkeep is not on the server list right now. The figures below are from when it was last seen, 38d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
Google Cloud Rust JP | 3X | 48H Upkeep's wipe history is too thin on record to show a rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. The world you are playing on was built 70 days 2 hours.
These are the Rust Live Stats lists Google Cloud Rust JP | 3X | 48H Upkeep fits: 3x Rust servers live now and Modded Rust servers live now. These filters on the server list bring it up: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
gmrust (Game mode): Standard survival, in the Rust style; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2632 (Protocol): Join only if your game is on protocol 2632; cs161125 (Build): The game build is 161125; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded: plugins or changed settings alter the game: that is the tag list Google Cloud Rust JP | 3X | 48H Upkeep publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Google Cloud Rust JP | 3X | 48H Upkeep is not online at the moment, having last been seen 38 days 8 hours ago.
Ranked by seven-day player hours, Google Cloud Rust JP | 3X | 48H Upkeep is #15,490, placing it in the top 70% of ranked servers.
The name says it: gathering runs at 3x on Google Cloud Rust JP | 3X | 48H Upkeep. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, and the browser lists it as Modded. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
Google Cloud Rust JP | 3X | 48H Upkeep runs a game-generated procedural map: size 3,500, seed 1829161776. RustMaps shows it from this page, since equal size and seed give an equal map.
The name points to Asia even though Google Cloud Rust JP | 3X | 48H Upkeep publishes no region tag. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 136.110.109.59:28015 is its address.
The setup on Google Cloud Rust JP | 3X | 48H Upkeep is Rust network protocol 2632 and build 161125 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Google Cloud Rust JP | 3X | 48H Upkeep is currently offline, with its last appearance 38 days 8 hours ago. It was online for 0 of 168 hours in the last 7 full days, or 0% of the time. On 13 September 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 136.110.109.59:28015.