Skip to the content
Dive report

Google Cloud Rust JP | 3X | 48H Upkeep

Offline 136.110.109.59:28015 checked 27d ago

3x moddedoxide
Drop in
0/ 20 players now 0% full
07-day averagepeak –
#15,490ranktop 70%
58d agolast wipeno schedule published
–next wipeno wipe seen yet

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

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
WipedPeakCrowdLastedPlayers 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and listings

Where does Google Cloud Rust JP | 3X | 48H Upkeep appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers, tracked live and Modded Rust servers. Its entry appears under the filters Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.

How should you read the tags on Google Cloud Rust JP | 3X | 48H Upkeep?

The server browser shows these tags for Google Cloud Rust JP | 3X | 48H Upkeep: gmrust (Game mode): This is the standard Rust survival experience; mp20 (Max players): The slot count is 20; ts8 (Group limit): The default team size of 8 applies here; v2632 (Protocol): This server runs game protocol 2632, so your game must match that version to join; cs161125 (Build): The build number is 161125; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

Server details

What's the location of Google Cloud Rust JP | 3X | 48H Upkeep?

The name of Google Cloud Rust JP | 3X | 48H Upkeep points to Asia, even without a region tag. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 136.110.109.59:28015.

What's the uptime like for Google Cloud Rust JP | 3X | 48H Upkeep?

The server Google Cloud Rust JP | 3X | 48H Upkeep is not reachable at the moment; the last sighting was 27 days 3 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 13 September 2026.

What Rust version is Google Cloud Rust JP | 3X | 48H Upkeep on?

The version on Google Cloud Rust JP | 3X | 48H Upkeep is Rust network protocol 2632 and build 161125, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.

Wipe schedule

What schedule does Google Cloud Rust JP | 3X | 48H Upkeep follow for wipes?

Google Cloud Rust JP | 3X | 48H Upkeep's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 58 days 21 hours is how long ago this world came into being.

Map and rules

What settings are in place on Google Cloud Rust JP | 3X | 48H Upkeep?

At 3x gather, Google Cloud Rust JP | 3X | 48H Upkeep does what its name suggests. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.

What's the map on Google Cloud Rust JP | 3X | 48H Upkeep?

A game-generated procedural map of size 3,500 with seed 1829161776 is in play on Google Cloud Rust JP | 3X | 48H Upkeep. You can see it on RustMaps from this page, since the same size and seed produce the same map.

Player count

What's the population like on Google Cloud Rust JP | 3X | 48H Upkeep?

Right now Google Cloud Rust JP | 3X | 48H Upkeep is offline, with its last appearance 27 days 3 hours ago.

What position does Google Cloud Rust JP | 3X | 48H Upkeep hold in the server rankings?

For player hours in the last seven days, Google Cloud Rust JP | 3X | 48H Upkeep ranks #15,490, within the top 70% of ranked servers.

How to join

What's the process to join Google Cloud Rust JP | 3X | 48H Upkeep?

Open Rust and press F1, then type client.connect 136.110.109.59:28015. Alternatively, click Launch Rust on this page to join via Steam.

What each one means

Server tags

Published as mp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z

Game

gmrust
Game mode This is the standard Rust survival experience.
mp20
Max players The slot count is 20.
ts8
Group limit The default team size of 8 applies here.
v2632
Protocol This server runs game protocol 2632, so your game must match that version to join.
cs161125
Build The build number is 161125.
ptrak
Networking Standard RakNet networking.
$r?
Region code It has no region code.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded You'll see it in Modded, since plugins or settings modify the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.