Statistical profileOffline
Google Cloud Rust JP | 3X | 48H Upkeep
136.110.109.59:28015 checked 37d ago
Connect to this server
1. Main points
Players now
0/ 20
0% full
7-day average
0
peak –
Rank
#15,490
top 70%
Last wipe
69d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 20 slots.
- It ranks #15,490 of all ranked servers, the top 70%, on player hours over the last seven days.
- Its current map went up 69d ago.
2. Players
Figure 1: Players on Google Cloud Rust JP | 3X | 48H Upkeep
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Google Cloud Rust JP | 3X | 48H Upkeep
3500 · seed 1829161776
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 3500 |
| Seed | 1829161776 |
8. Server characteristics
Table 3: Characteristics of Google Cloud Rust JP | 3X | 48H Upkeep
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 8 / 300 |
| Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long | EA · groups of 100+ · 3x · monthly · 7 on average | 4 / 120 |
| HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP | EA · groups of 8+ · 3x · monthly · 2 on average | 0 / 75 |
| 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3 | EA · groups of 8+ · 3x · 1 on average | 0 / 50 |
| [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 81 on average | 18 / 115 |
| [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 25 on average | 2 / 150 |
10. Quick answers
From the figures on this page.
Wipe records
This release records the wipe timetable for Google Cloud Rust JP | 3X | 48H Upkeep: what is it?
Too few wipes of Google Cloud Rust JP | 3X | 48H Upkeep are on record to establish its rhythm. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. The present world dates from 69 days 13 hours.
About the server
Is Google Cloud Rust JP | 3X | 48H Upkeep up, and how well has it held up?
Last seen 37 days 19 hours ago, Google Cloud Rust JP | 3X | 48H Upkeep is offline in this release. 0 of 168 hours on across the last 7 full days gives an uptime of 0%. First recorded by Rust Census on 13 September 2026.
Which location does Google Cloud Rust JP | 3X | 48H Upkeep run from?
No region tag is published by Google Cloud Rust JP | 3X | 48H Upkeep, but its name points to Asia. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 136.110.109.59:28015 is its address.
What version of Rust has been recorded on Google Cloud Rust JP | 3X | 48H Upkeep?
The version in use on Google Cloud Rust JP | 3X | 48H Upkeep is Rust network protocol 2632 and build 161125 on Linux. Steam updates your game for you, but it has to be on the same protocol to join.
Population
What are the current player figures for Google Cloud Rust JP | 3X | 48H Upkeep?
At this release Google Cloud Rust JP | 3X | 48H Upkeep is offline, having last been seen 37 days 19 hours ago.
In the rankings of Rust servers, where is Google Cloud Rust JP | 3X | 48H Upkeep placed?
The rank for Google Cloud Rust JP | 3X | 48H Upkeep is #15,490 on seven-day player hours, in the top 70% of ranked servers.
Lists and tags
Where does Google Cloud Rust JP | 3X | 48H Upkeep appear among the Rust Census lists and filters?
These Rust Census lists include Google Cloud Rust JP | 3X | 48H Upkeep: 3x Rust servers, counted and Modded Rust servers, counted. 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.
Which meanings do the tags on Google Cloud Rust JP | 3X | 48H Upkeep carry?
These are the tags Google Cloud Rust JP | 3X | 48H Upkeep publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp20 (Max players): Slots: 20; ts8 (Group limit): 8 per team, which is the game's default limit; v2632 (Protocol): To connect, your game version must match protocol 2632; cs161125 (Build): Build 161125 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Modded: the game is changed by plugins or settings. At the top of this page you will find the tags for current players, queue and world creation time.
Rules, map
Which map has been recorded for Google Cloud Rust JP | 3X | 48H Upkeep?
Size 3,500 and seed 1829161776: that is the procedural map on Google Cloud Rust JP | 3X | 48H Upkeep, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
What settings and rules have been listed for Google Cloud Rust JP | 3X | 48H Upkeep?
The name of Google Cloud Rust JP | 3X | 48H Upkeep records a gather rate of 3x. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat is active: VAC, Valve's system, is on.
Join details
What steps are needed to join Google Cloud Rust JP | 3X | 48H Upkeep?
Enter client.connect 136.110.109.59:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp20,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp20 | Max players Slots: 20. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2632 | Protocol To connect, your game version must match protocol 2632. |
cs161125 | Build Build 161125 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.