gitsync-oxide
Offline 125.236.230.198:28015 checked 14d ago
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
- 17/ 100
- 295/ 400
- 175/ 225
- 120/ 100
- 363/ 1000
- 26/ 700
Quick answers
Tags and search
Where does gitsync-oxide appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include gitsync-oxide: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on gitsync-oxide?
The server browser shows these tags for gitsync-oxide: gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): There are 2 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166652 (Build): It's on build 166652; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
Where can you find gitsync-oxide?
There is no published region for gitsync-oxide. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 125.236.230.198:28015.
How reliable is gitsync-oxide?
Right now gitsync-oxide is offline, having last been seen 14 days 6 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 3 October 2026.
What is the Rust version for gitsync-oxide?
Rust network protocol 2634 and build 166652 is what gitsync-oxide runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does gitsync-oxide wipe?
The wipes recorded for gitsync-oxide are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 14 days 11 hours ago.
Settings and map
What settings are in place on gitsync-oxide?
No gather rate appears in the name of gitsync-oxide. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on gitsync-oxide?
gitsync-oxide uses a game-generated procedural map.
Player stats
How many players are on gitsync-oxide?
Right now gitsync-oxide is offline, with its last appearance 14 days 6 hours ago.
Where does gitsync-oxide sit in the rankings?
For player hours in the last seven days, gitsync-oxide ranks #15,986, within the top 71% of ranked servers.
How to join
How do you get into gitsync-oxide?
To join, open Rust, hit F1, and enter client.connect 125.236.230.198:28015. Or click Launch Rust on this page to open the game through Steam and connect.