Offline 125.236.230.198:28015 checked 25d ago
gitsync-oxide
Connect
srv = rust.server("125.236.230.198:28115")
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 71% 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:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 22:40 UTC
- hostname
- –
- first seen
- 3 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 | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 96/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 34/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 103/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 346/350 |
Quick answers
From the figures on this page.
Population
How does gitsync-oxide compare in the rankings?
Rank #15,986 on seven-day player hours for gitsync-oxide, within the top 71% of all ranked servers.
What population does gitsync-oxide carry?
gitsync-oxide returns no live count at this refresh, having last been seen 25 days 17 hours ago.
Server facts
Which Rust version is gitsync-oxide on?
Version Rust network protocol 2634 and build 166652 on Linux is reported by gitsync-oxide. Joining needs the same protocol on your game; Steam handles the update.
How reliable is gitsync-oxide, and is it up?
Offline now for gitsync-oxide, last seen 25 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 3 October 2026.
Where does gitsync-oxide sit?
No region is published by gitsync-oxide. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 125.236.230.198:28015 is its address.
Map and rules
Which settings and rules does gitsync-oxide run?
No gather rate appears in the name: gitsync-oxide. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. 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.
What is the map on gitsync-oxide?
A procedural map runs on gitsync-oxide, generated by the game.
Wipe schedule
When does gitsync-oxide wipe, and on what schedule?
The record for gitsync-oxide holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 25 days 23 hours ago, and that is the one in play.
Tags, lists
Which Rust Data filters and lists contain gitsync-oxide?
The Rust Data lists that gitsync-oxide fits are: 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.
Which meanings do the tags on gitsync-oxide hold?
These tags are published by gitsync-oxide and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to gitsync-oxide?
Enter client.connect 125.236.230.198:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.