Google Cloud Rust JP | 3X | 48H Upkeep
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 37d ago · 136.110.109.59:28015
Abstract
We describe the public Rust server Google Cloud Rust JP | 3X | 48H Upkeep, reached at 136.110.109.59:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,490 of all servers, the top 70%. It last wiped 69d ago.
Keywords3x gather modded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 136.110.109.59:28015 |
|---|---|
| Region | – |
| Max players | 20 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 20 Aug 2026, 11:29 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3500 |
| Seed | 1829161776 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust servers with 3x gather [2], modded Rust population table [3] and upcoming Rust wipes [4].
| Server | Players |
|---|---|
| Japan Tokyo - Limited Raid Hours |3x|PvP|JPEA · groups of 8+ · 3x · weekly · 40 on average | 11/300 |
| Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|LongEA · groups of 100+ · 3x · monthly · 7 on average | 7/120 |
| HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORPEA · groups of 8+ · 3x · monthly · 2 on average | 0/75 |
| 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3EA · groups of 8+ · 3x · 1 on average | 0/50 |
| [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 81 on average | 25/115 |
| [SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 25 on average | 3/150 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1What is the location of Google Cloud Rust JP | 3X | 48H Upkeep?
No region tag is published by Google Cloud Rust JP | 3X | 48H Upkeep, but its name points to Asia. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 136.110.109.59:28015.
A.2What is the online status and reliability of Google Cloud Rust JP | 3X | 48H Upkeep?
At the present moment, Google Cloud Rust JP | 3X | 48H Upkeep is offline; it was last seen 37 days 21 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 13 September 2026.
A.3What version of Rust is run on Google Cloud Rust JP | 3X | 48H Upkeep?
The version of Rust on Google Cloud Rust JP | 3X | 48H Upkeep is network protocol 2632 and build 161125, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.
Wipe timing
A.4On what cycle does Google Cloud Rust JP | 3X | 48H Upkeep wipe?
The record of Google Cloud Rust JP | 3X | 48H Upkeep's wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 69 days 15 hours have passed since the current world was generated.
Player count
A.5How does Google Cloud Rust JP | 3X | 48H Upkeep compare with other Rust servers in the rankings?
The seven-day player-hours ranking puts Google Cloud Rust JP | 3X | 48H Upkeep at #15,490, within the top 70% of ranked servers.
A.6What is the population level of Google Cloud Rust JP | 3X | 48H Upkeep?
The last recorded sighting of Google Cloud Rust JP | 3X | 48H Upkeep was 37 days 21 hours ago; it is offline now.
Tags and filters
A.7What is the meaning of the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
gmrust (Game mode): This is survival as standard Rust plays; mp20 (Max players): It offers 20 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2632 (Protocol): Your game must run protocol 2632 to connect; cs161125 (Build): The game build is 161125; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Google Cloud Rust JP | 3X | 48H Upkeep publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.8Where can Google Cloud Rust JP | 3X | 48H Upkeep be found among the Rust Statistics lists and filters?
The Rust Statistics lists that Google Cloud Rust JP | 3X | 48H Upkeep fits are: Rust servers with gather rate 3x and Modded Rust servers. It appears under the following filters 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 map
A.9Under what rules and settings does Google Cloud Rust JP | 3X | 48H Upkeep operate?
The rate for gathering on Google Cloud Rust JP | 3X | 48H Upkeep is 3x, according to its name. The group cap is 8 players, which is the default in the game. The mode is survival, which means the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.
A.10On which map does Google Cloud Rust JP | 3X | 48H Upkeep take place?
Generated by the game from seed 1829161776, the procedural map on Google Cloud Rust JP | 3X | 48H Upkeep measures 3,500. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
How to join
A.11What is the process for joining Google Cloud Rust JP | 3X | 48H Upkeep?
Press F1 inside Rust to open the console and enter client.connect 136.110.109.59:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. This is survival as standard Rust plays. |
mp20 | Max players. It offers 20 slots. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2632 | Protocol. Your game must run protocol 2632 to connect. |
cs161125 | Build. The game build is 161125. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. A region code has not been set. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: 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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Rust servers with 3x gather. ruststatistics.org/top-3x-rust-servers.
- [3]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
- [4]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.