Offline136.110.109.59:28015checked 23d ago
Google Cloud Rust JP | 3X | 48H Upkeep
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
daily · 1 is bestTop 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| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules, map and settings
What configuration does Google Cloud Rust JP | 3X | 48H Upkeep use?
Google Cloud Rust JP | 3X | 48H Upkeep sets its gather rate to 3x, as its name states. The group limit is the game's default of 8 players. survival is the game mode, gather, build, raid: the standard game. Fighting and raiding between players is allowed. The server browser lists it as Modded, with plugins or settings that alter the game. Plugins: Oxide. Anti-cheat VAC from Valve is on.
Which map is running on Google Cloud Rust JP | 3X | 48H Upkeep?
The game generates a procedural map of size 3,500 with seed 1829161776 for Google Cloud Rust JP | 3X | 48H Upkeep. You can see it on RustMaps from this page, because the same size and seed give the same map.
Server tags
Where can Google Cloud Rust JP | 3X | 48H Upkeep be found in Rust Player Count lists and filters?
The Rust Player Count lists that Google Cloud Rust JP | 3X | 48H Upkeep fits are: 3x Rust servers and Modded Rust servers. You can find it on the server list using these filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 3x.
How should you interpret the tags on Google Cloud Rust JP | 3X | 48H Upkeep?
For the game's server browser, Google Cloud Rust JP | 3X | 48H Upkeep publishes: gmrust (Game mode): The usual Rust survival experience; mp20 (Max players): 20 slots are available; ts8 (Group limit): This uses the default team cap: 8 players; v2632 (Protocol): Joining requires the same protocol: 2632; cs161125 (Build): Build number: 161125; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): A region code is not present; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): It appears under Modded because plugins or settings modify the game. The tags also include its current players, its queue and when its world was made, shown at the top of this page.
Player numbers
How many players does Google Cloud Rust JP | 3X | 48H Upkeep have?
Google Cloud Rust JP | 3X | 48H Upkeep is offline at the moment; the last time it was seen was 23 days 3 hours ago.
How does Google Cloud Rust JP | 3X | 48H Upkeep compare in server rankings?
For player hours in the last seven days, Google Cloud Rust JP | 3X | 48H Upkeep ranks #15,490 and is in the top 70% of all ranked servers.
Server details
What is the online status and reliability of Google Cloud Rust JP | 3X | 48H Upkeep?
Google Cloud Rust JP | 3X | 48H Upkeep is down at the moment and was last seen 23 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. Its first appearance in Rust Player Count was on 13 September 2026.
What Rust version is used on Google Cloud Rust JP | 3X | 48H Upkeep?
Linux hosts Google Cloud Rust JP | 3X | 48H Upkeep, which runs Rust network protocol 2632 and build 161125. The protocol has to match for you to join, but Steam updates it without any action from you.
What region does Google Cloud Rust JP | 3X | 48H Upkeep serve?
Its name points to Asia, even though Google Cloud Rust JP | 3X | 48H Upkeep publishes no region tag. The location shown by Rust Player Count is the one a server provides; it does not verify where the machine actually is. You can reach it at 136.110.109.59:28015.
Wipe information
When does Google Cloud Rust JP | 3X | 48H Upkeep wipe?
The rhythm of wipes on Google Cloud Rust JP | 3X | 48H Upkeep cannot be told yet, since too few are on record. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. It has been running its current world for 54 days 21 hours.
Join the server
How can I connect to Google Cloud Rust JP | 3X | 48H Upkeep?
To get in, press F1 in Rust and enter client.connect 136.110.109.59:28015. You can also click Launch Rust here, which opens the game through Steam and brings you onto the server.
Server tags
what each one meansPublished 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.