ghtime67
Key statistics
the figures behind the quote- Players now
- 0/ 500 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,977 top 71%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 2d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 Oct 2026 no hostname published
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 0 players, 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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 11 Oct, 03:49 UTC2d ago | 0 | – | running | 0 |
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 wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 51/300 | ▲+15+40.0% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 87/245 | ▲+45+106.3% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 88/100 | ▼−3−3.2% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 40/1000 | ▼−13−24.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 11/1000 | ▼−10−47.4% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average | 57/700 | ▼−38−39.9% |
Quick answers
from the figures on this pageRules & Settings
How is ghtime67 configured in terms of rules and settings?
The name of ghtime67 carries no gather rate. Up to 8 players per group, which is the game's default. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are running. VAC is active.
Which map is played on ghtime67?
ghtime67 uses a procedural map, which the game generates.
Population
What position does ghtime67 hold in the server rankings?
In the top 71% of all ranked servers, ghtime67 is #15,977 on player hours over the last seven days.
What is the population on ghtime67?
At present, ghtime67 is offline; the last sighting was 2 days 17 hours ago. Average players over the last seven days: 0.
Wipe Frequency
How does ghtime67 handle wipe day?
An average of 0 players marked the busiest point of its recent wipes. On the latest wipe, 0 hours after the wipe, the crowd peaked.
How often does ghtime67 wipe?
No rhythm can be told for ghtime67 yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. Its world now is 2 days 17 hours old.
Server Info
Where can ghtime67 be found?
No region is published by ghtime67. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 45.147.123.58:28015.
What Rust version is ghtime67 running?
The build is Rust network protocol 2634 and build 167398 on Windows, running on ghtime67. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of ghtime67?
No response from ghtime67. It was last seen 2 days 17 hours ago. The last 2 full days give 2% uptime, 1 hours on out of 48. First sighting by Rust Analytics: 10 October 2026.
Tags and Rankings
How should you interpret the tags on ghtime67?
Published by ghtime67 for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp500 (Max players): Capacity: 500 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167398 (Build): It runs build 167398; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does ghtime67 show up in Rust Analytics lists and filters?
These Rust Analytics lists include ghtime67: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Joining the Server
What is the process to join ghtime67?
Type client.connect 45.147.123.58:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp500,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp500
ts8
v2634
cs167398
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.