Station XX-15861 · no signal
ghtime67
Offline 45.147.123.58:28015 checked 16d ago
- Players now
- 0/ 500
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,861
- top 72%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 500 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 11 Oct, 03:49 UTC16d ago | M0.0■steady | 0 | – | – | running | 0 |
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 ghtime67?
ghtime67 uses a procedural map, which the game generates.
Which settings and rules apply on ghtime67?
No gather rate appears in the name of ghtime67. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.
Population
How many players are recorded on ghtime67 right now?
ghtime67 is not responding at this moment and is offline, last seen 16 days 23 hours ago.
How does ghtime67 rank against other Rust servers?
On player hours for the past week, ghtime67 sits at #15,861, which puts it inside the top 72% of every ranked server.
Operator and location
How reliably does ghtime67 stay online?
ghtime67 is down at the moment; the last recorded contact was 16 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 10 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does ghtime67 run from?
A region is not published by ghtime67. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 45.147.123.58:28015.
What build of Rust does ghtime67 use?
ghtime67 is running Rust network protocol 2634 and build 167398 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on ghtime67?
On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does ghtime67 wipe, and on which days?
The rhythm of ghtime67 cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 16 days 23 hours.
Lists and tags
What do the server tags on ghtime67 mean?
Tags published by ghtime67 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp500 (Max players): Slots: 500; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167398 (Build): Game build: 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 ghtime67 appear?
These Rust Server Trends lists include ghtime67: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to ghtime67?
Enter client.connect 45.147.123.58:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.