Offline 125.236.230.198:29015 checked 5d ago
gitsync-oxide
Connect
srv = rust.server("125.236.230.198:29115")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 125.236.230.198:29015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 22:40 UTC
- hostname
- –
- first seen
- 4 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 62/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 132/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 36/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 95 on average | 107/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 109/200 |
Quick answers
From the figures on this page.
Population
How does gitsync-oxide compare in the rankings?
Rank #15,257 on seven-day player hours for gitsync-oxide, within the top 69% of all ranked servers.
How many players does gitsync-oxide hold at once?
The current row shows gitsync-oxide offline; the last response was 5 days 4 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is gitsync-oxide on?
Rust network protocol 2634 and build 166652 on Linux is what gitsync-oxide runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is gitsync-oxide, and is it up?
The latest sample has gitsync-oxide offline, with a last sighting 5 days 4 hours ago. Over the last 7 full days the hours up number 2 of 168, 1%. Its earliest recorded date in Rust Data is 4 October 2026.
In which location is gitsync-oxide hosted?
For gitsync-oxide, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 125.236.230.198:29015 is its address.
Map and rules
Which settings and rules does gitsync-oxide run?
You will not find a gather rate in the string gitsync-oxide. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has gitsync-oxide loaded?
gitsync-oxide runs a procedural map, which the game generates.
Wipes and dates
When does gitsync-oxide wipe, and how often?
The record for gitsync-oxide holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 26 days 10 hours ago.
Tags and filters
Which Rust Data filters and lists contain gitsync-oxide?
These Rust Data lists include 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.
How should you read the server tags on gitsync-oxide?
The game's server browser reads these tags from gitsync-oxide: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to gitsync-oxide?
In Rust, F1 opens the console: type client.connect 125.236.230.198:29015. Launch Rust on this page does the same by opening the game through Steam and connecting.