RUST METRICSFlight deck · live data
Data live Servers11,706 Players60,014 Populated3,275 Fresh wipes 3 h164 Scan5 min
‹ All servers125.236.230.198:29015
Offline Full Queue Fresh wipe Wipe due No query

gitsync-oxide

Offline 125.236.230.198:29015 checked 4d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,262top 69%
Last wipe26d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct14 Oct26 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

How often does gitsync-oxide wipe, and when?

Its rhythm cannot be told from the wipes of gitsync-oxide on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 26 days 2 hours ago the current world was made.

Tags

Which tags does gitsync-oxide carry, and what do they mean?

These are the tags gitsync-oxide publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does gitsync-oxide appear in Rust Metrics lists and filters?

Rust Metrics lists featuring gitsync-oxide: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does gitsync-oxide sit in the rankings?

Player hours over seven days put gitsync-oxide at #15,262, in the top 69% of all ranked servers.

How full does gitsync-oxide get?

Status for gitsync-oxide: offline. Last seen 4 days 20 hours ago. A seven-day average of 0 players is the reading.

Server

What location is gitsync-oxide hosted in?

Reading: location. gitsync-oxide gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 125.236.230.198:29015.

What Rust version is gitsync-oxide on?

Reading: gitsync-oxide, Rust network protocol 2634 and build 166652, Linux. Matching protocol is required to join. Let Steam update your game.

How reliable is gitsync-oxide, and is it online now?

Reading: offline. gitsync-oxide last answered 4 days 20 hours ago. Uptime for the last 7 full days: 2 of 168 hours, or 1%. The first sighting on Rust Metrics was 4 October 2026.

Settings and map

What rules does gitsync-oxide enforce, and what are its settings?

No gather rate appears in the name: gitsync-oxide. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is gitsync-oxide on?

The game generates a procedural map for gitsync-oxide.

Join

How can you get onto gitsync-oxide?

To join: start Rust, press F1 and type client.connect 125.236.230.198:29015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players 2 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.