Station XX-15490 · no signal
Google Cloud Rust JP | 3X | 48H Upkeep
Offline 136.110.109.59:28015 checked 37d ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,490
- top 70%
- Last wipe
- 69d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M –not enough readings
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 pageServer rules
Which map is running on Google Cloud Rust JP | 3X | 48H Upkeep?
Generated by the game, the map on Google Cloud Rust JP | 3X | 48H Upkeep is procedural, size 3,500 with seed 1829161776. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Google Cloud Rust JP | 3X | 48H Upkeep?
Going by its name, Google Cloud Rust JP | 3X | 48H Upkeep runs 3x gather. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Google Cloud Rust JP | 3X | 48H Upkeep right now?
Google Cloud Rust JP | 3X | 48H Upkeep is not responding at this moment and is offline, last seen 37 days 19 hours ago.
How does Google Cloud Rust JP | 3X | 48H Upkeep rank against other Rust servers?
On player hours for the past week, Google Cloud Rust JP | 3X | 48H Upkeep sits at #15,490, which puts it inside the top 70% of every ranked server.
Operator and location
How reliably does Google Cloud Rust JP | 3X | 48H Upkeep stay online?
Google Cloud Rust JP | 3X | 48H Upkeep is down at the moment; the last recorded contact was 37 days 19 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does Google Cloud Rust JP | 3X | 48H Upkeep run from?
Its name points to Asia, but Google Cloud Rust JP | 3X | 48H Upkeep publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 136.110.109.59:28015.
What build of Rust does Google Cloud Rust JP | 3X | 48H Upkeep use?
Google Cloud Rust JP | 3X | 48H Upkeep is running Rust network protocol 2632 and build 161125 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
On what timetable does Google Cloud Rust JP | 3X | 48H Upkeep run its wipes?
Too few wipes of Google Cloud Rust JP | 3X | 48H Upkeep are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 69 days 13 hours.
Server tags
What do the server tags on Google Cloud Rust JP | 3X | 48H Upkeep mean?
The game's server browser reads the tags Google Cloud Rust JP | 3X | 48H Upkeep publishes: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): 20 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2632 (Protocol): Your game needs to be on protocol 2632 to join; cs161125 (Build): The game build is 161125; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Google Cloud Rust JP | 3X | 48H Upkeep appear?
The Rust Server Trends lists that take in Google Cloud Rust JP | 3X | 48H Upkeep are: 3x Rust servers, by live population and Modded Rust servers, tracked live. 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.
Join the server
How do you connect to Google Cloud Rust JP | 3X | 48H Upkeep?
To join, enter client.connect 136.110.109.59:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.