gitsync-oxide

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 25d ago · 125.236.230.198:28015

Abstract

We describe the public Rust server gitsync-oxide, reached at 125.236.230.198:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,986 of all servers, the top 71%. It last wiped 25d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/2	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,986	top 71%
Last wipe	25d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

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

Figure 2: 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.

4Rank

The server stands in the top 71% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

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

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

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
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and predicted wipe schedule [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 150 on average	40/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	128/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 120 on average	84/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average	34/700
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average	87/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 85 on average	301/310

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of gitsync-oxide?

There is no region published for gitsync-oxide. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 125.236.230.198:28015.

A.2How reliable is gitsync-oxide, and is it currently online?

At the present moment, gitsync-oxide is offline; it was last seen 25 days 18 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 3 October 2026.

A.3What is the Rust version for gitsync-oxide?

Rust network protocol 2634 and build 166652 is the version that gitsync-oxide runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does gitsync-oxide follow for wipes?

The record of gitsync-oxide's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 25 days 23 hours ago.

Population

A.5What position does gitsync-oxide occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts gitsync-oxide at #15,986, within the top 71% of ranked servers.

A.6How would you characterise the player activity on gitsync-oxide?

The last recorded sighting of gitsync-oxide was 25 days 18 hours ago; it is offline now.

Tags, lists

A.7How should the tags on gitsync-oxide be interpreted?

Tags from gitsync-oxide, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can gitsync-oxide be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that gitsync-oxide fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.9What are the settings and rules that govern gitsync-oxide?

The name of gitsync-oxide states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

A.10On which map does gitsync-oxide take place?

A procedural map, generated by the game, is what gitsync-oxide runs.

Connection

A.11What is the process for joining gitsync-oxide?

Enter client.connect 125.236.230.198:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp2`	Max players. 2 slots are available.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs166652`	Build. The game build is 166652.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Plugins are handled by Oxide (uMod).
`^z`	Modded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.