gitsync-oxide
Key statistics
the figures behind the quote- Players now
- 0/ 2 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,922 top 72%
- Rank · 7d ago
- #16,709 ▲787 places up
- Last wipe
- 11d ago no schedule published
- Next wipe
- – no wipe 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
- 4 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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 wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 129 on average | 36/300 | ▲+22+161.3% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 36/225 | ▲+10+37.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▲+1+0.7% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 88 on average | 8/1000 | ▼−4−32.3% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 5/1000 | ▲+1+37.5% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 18/700 | ▲+5+39.4% |
Quick answers
from the figures on this pageMap and Rules
How is gitsync-oxide configured in terms of rules and settings?
No gather rate is given in the name of gitsync-oxide. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. PvP and raiding are enabled. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Oxide. VAC is active.
Which map is played on gitsync-oxide?
A procedural map runs on gitsync-oxide, created by the game.
Population
What is the rank of gitsync-oxide?
In the top 72% of all ranked servers, gitsync-oxide is #15,922 on player hours over the last seven days.
How full is gitsync-oxide?
At present, gitsync-oxide is offline; the last sighting was 6 days 13 hours ago. Average players over the last seven days: 0.
Wipe Cycle
How often does gitsync-oxide wipe?
The record holds too few of gitsync-oxide's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. Its world now is 11 days old.
Server Details
What is the location of gitsync-oxide?
For gitsync-oxide, no region is published. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 125.236.230.198:29015 is its address.
What Rust version is gitsync-oxide running?
The version in use at gitsync-oxide: Rust network protocol 2634 and build 166652, on Linux. Joining requires the same protocol on your game, which Steam updates.
Is gitsync-oxide up, and how consistent is its uptime?
Offline at this moment: gitsync-oxide. Last seen 6 days 13 hours ago. 7 full days have passed with 8% uptime, 14 of 168 hours. The earliest Rust Analytics saw it was 4 October 2026.
Tags and Rankings
How should you interpret the tags on gitsync-oxide?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp2 (Max players): It holds 2 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which gitsync-oxide publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does gitsync-oxide show up in Rust Analytics lists and filters?
These Rust Analytics lists include gitsync-oxide: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connection
What is the process to join gitsync-oxide?
Type client.connect 125.236.230.198:29015 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 mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp2
ts8
v2634
cs166652
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.