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,986 top 71%
- Rank · 7d ago
- #16,953 ▲967 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
- 3 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
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 | 20/300 | ▼−12−36.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 109 on average | 19/225 | ▼−9−31.7% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 89/100 | ▼−2−1.7% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 3/1000 | ▼−7−68.7% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 75 on average | 1/1000 | ▪+0 | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 5/700 | ▼−10−67.7% |
Quick answers
from the figures on this pageServer Rules
How is gitsync-oxide configured in terms of rules and settings?
No gather rate appears in the name of gitsync-oxide. 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. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are running. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on gitsync-oxide?
The game generates the procedural map on gitsync-oxide.
Activity
Where does gitsync-oxide sit in the rankings?
For the last seven days, gitsync-oxide holds rank #15,986 on player hours, in the top 71% of all ranked servers.
How full is gitsync-oxide?
Right now, gitsync-oxide is offline; the last sighting was 11 days ago.
Wipe Schedule
On what cycle does gitsync-oxide wipe?
No rhythm can be told for gitsync-oxide yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 11 days 5 hours ago the current world was created.
Server Details
What is the location of gitsync-oxide?
For gitsync-oxide, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 125.236.230.198:28015 is its address.
gitsync-oxide runs which version of Rust?
The version in use at gitsync-oxide: Rust network protocol 2634 and build 166652, on Linux. The protocol has to match for you to join, and Steam applies that update.
How reliable is gitsync-oxide and is it currently online?
No response from gitsync-oxide. It was last seen 11 days ago. 7 full days have passed with 0% uptime, 0 of 168 hours. First sighting by Rust Analytics: 3 October 2026.
Tags and Rankings
How should you interpret the tags on gitsync-oxide?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp2 (Max players): Slot count: 2; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): Game build: 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none 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?
The following Rust Analytics lists feature gitsync-oxide: 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 2 weeks.
Connection
What is the process to join gitsync-oxide?
Type client.connect 125.236.230.198: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 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.