Skip to the shelves
Rust Vending Machine 89,109playing
Modded#15,490

Google Cloud Rust JP | 3X | 48H Upkeep

Offline 136.110.109.59:28015 checked 22d ago

3x moddedoxide
players now0of 20 slots
7-day average0peak –
rank#15,490top 70%
last wipe · restocked54d agono schedule published
next wipe · restock–no 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.

Also on the shelf

Similar servers

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

On the back of the pack

Quick answers

From the figures on this page.

Lists and tags

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

gmrust (Game mode): The standard survival game mode; mp20 (Max players): The cap is 20; ts8 (Group limit): Teams cap at 8, the standard game limit; v2632 (Protocol): To join, your game version must line up with protocol 2632; cs161125 (Build): Game build: 161125; ptrak (Networking): The game's usual network layer, RakNet, is used; $r? (Region code): Region code not set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Modded: plugins or settings change how it plays is what Google Cloud Rust JP | 3X | 48H Upkeep tags itself with, and the server browser takes note. Tags also carry its current players, its queue and when the world was made, all up top on this page.

On Rust Vending Machine, which lists and filters can you find Google Cloud Rust JP | 3X | 48H Upkeep in?

The Rust Vending Machine lists that feature Google Cloud Rust JP | 3X | 48H Upkeep are: 3x Rust servers and Modded Rust servers. 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.

Settings and rules

Which map is currently on Google Cloud Rust JP | 3X | 48H Upkeep?

A procedural map, size 3,500 with seed 1829161776, generated by the game, is what Google Cloud Rust JP | 3X | 48H Upkeep runs. You can view it on RustMaps from this page, since the same size and seed give the same map.

What rules does Google Cloud Rust JP | 3X | 48H Upkeep enforce, and what settings does it run?

Its name shows a 3x gather rate for Google Cloud Rust JP | 3X | 48H Upkeep. 8 players is the default group size, and that is the cap here. survival is the game mode, gather, build, raid: the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings alter the game. You will find Oxide plugins running here. VAC, Valve's anti-cheat, is enabled.

Server details

Where can you find 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. A server's stated location is what Rust Vending Machine shows; the actual machine location is not looked up. The endpoint is 136.110.109.59:28015.

What is the uptime like on Google Cloud Rust JP | 3X | 48H Upkeep?

No stock on Google Cloud Rust JP | 3X | 48H Upkeep at the moment, last seen 22 days 13 hours ago. 0 of 168 hours online over the last 7 full days, or 0% uptime. Its first record on Rust Vending Machine is dated 13 September 2026.

What version does Google Cloud Rust JP | 3X | 48H Upkeep use?

On Linux, Google Cloud Rust JP | 3X | 48H Upkeep is running Rust network protocol 2632 and build 161125. The protocol has to line up on your side to join, and Steam does the updating.

Player count

How does Google Cloud Rust JP | 3X | 48H Upkeep compare to other Rust servers in the rankings?

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

What is the current player count on Google Cloud Rust JP | 3X | 48H Upkeep?

Current status for Google Cloud Rust JP | 3X | 48H Upkeep: offline, last seen 22 days 13 hours ago.

Wipe schedule

How often does Google Cloud Rust JP | 3X | 48H Upkeep wipe?

Too few wipes of Google Cloud Rust JP | 3X | 48H Upkeep are recorded to tell what its rhythm is. On Thursday 5 November at 19:00 UTC the monthly force wipe comes, and every Rust server wipes. The world it has now started 54 days 7 hours ago.

Join the server

What steps do you take to join Google Cloud Rust JP | 3X | 48H Upkeep?

Open Rust and press F1 for the console, then type client.connect 136.110.109.59:28015. Or use the Launch Rust button here to open the game through Steam and connect.

Server tags

what each one means

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

Game

gmrust
Game mode The standard survival game mode.
mp20
Max players The cap is 20.
ts8
Group limit Teams cap at 8, the standard game limit.
v2632
Protocol To join, your game version must line up with protocol 2632.
cs161125
Build Game build: 161125.
ptrak
Networking The game's usual network layer, RakNet, is used.
$r?
Region code Region code not set.

Mods and access

^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Modded: plugins or settings change how it plays.

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.