This server publishes no banner
Exhibit no. 15,490Acc. 2026.15490
Google Cloud Rust JP | 3X | 48H Upkeep
Rust server · in the archive since 13 September 2026
Offline 136.110.109.59:28015 checked 37d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
The record of each wipe
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.
The rhythm
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Lists and tags
What do the server tags on Google Cloud Rust JP | 3X | 48H Upkeep mean?
The game's server browser reads these tags published by Google Cloud Rust JP | 3X | 48H Upkeep: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): Slot count: 20; ts8 (Group limit): Teams are capped at 8, the default the game ships; v2632 (Protocol): Your game must run protocol 2632 to join; cs161125 (Build): Build number: 161125; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The region code field is empty; ^o (Oxide): Oxide, also known as uMod, is the plugin framework in use; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. Shown at the top of this page are the current players, the queue and the world's age, also taken from the tags.
Which Rust Server History lists and filters include Google Cloud Rust JP | 3X | 48H Upkeep?
The Rust Server History lists that feature Google Cloud Rust JP | 3X | 48H Upkeep are: 3x Rust server list and Modded Rust servers: the record. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
The record
Which version of Rust does Google Cloud Rust JP | 3X | 48H Upkeep run?
The recorded build for Google Cloud Rust JP | 3X | 48H Upkeep is Rust network protocol 2632 and build 161125 on Linux. Steam updates your game for you; joining needs the same protocol.
Is Google Cloud Rust JP | 3X | 48H Upkeep online, and how reliable is it?
Offline now, Google Cloud Rust JP | 3X | 48H Upkeep was last seen 37 days 19 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0% of the time. First seen by Rust Server History on 13 September 2026.
Where is Google Cloud Rust JP | 3X | 48H Upkeep located?
Its name points to Asia, though Google Cloud Rust JP | 3X | 48H Upkeep publishes no region tag. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. You can reach it at 136.110.109.59:28015.
Wipe record
What is the wipe schedule on Google Cloud Rust JP | 3X | 48H Upkeep?
The rhythm of Google Cloud Rust JP | 3X | 48H Upkeep cannot be told yet, as too few of its wipes are on record. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. 69 days 14 hours ago its current world was made.
Player counts
How does Google Cloud Rust JP | 3X | 48H Upkeep rank against other Rust servers?
Player hours over the last seven days put Google Cloud Rust JP | 3X | 48H Upkeep at #15,490: a place in the top 70% of all ranked servers.
How busy is Google Cloud Rust JP | 3X | 48H Upkeep?
The last sighting of Google Cloud Rust JP | 3X | 48H Upkeep in the live count was 37 days 19 hours ago; it is offline now.
Map and rules
What are the rules and settings on Google Cloud Rust JP | 3X | 48H Upkeep?
The name states a 3x gather rate for Google Cloud Rust JP | 3X | 48H Upkeep. No group may exceed 8 players, the default set by the game. survival is the game mode, gather, build, raid: the standard game. You may fight and raid other players. Plugins or settings alter the game here, and the browser lists the server under Modded. Plugins in use: Oxide. VAC from Valve is switched on.
Which map does Google Cloud Rust JP | 3X | 48H Upkeep run?
Generated by the game at size 3,500 with seed 1829161776, the map on Google Cloud Rust JP | 3X | 48H Upkeep is procedural. You can look at the map on RustMaps from this page, since one size and seed always give one map.
Joining the server
How do I join Google Cloud Rust JP | 3X | 48H Upkeep?
Entering client.connect 136.110.109.59:28015 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.
The label explained
Server tags
What each tag this server publishes means.
Published as mp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
mp20
ts8
v2632
cs161125
ptrak
$r?
Mods and access
^o
^z
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.