Relics Dev Server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 125.254.123.81:28015

Abstract

We describe the public Rust server Relics Dev Server, reached at 125.254.123.81:28015. At the last check it held 1 of 10 places, against a seven-day mean of 0 and a peak of 2¹. It ranks #6,292 of all servers, the top 28%. It last wiped 27d 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	1/10	10% full
In the queue	0	no queue
Seven-day mean	0	peak 2, 48 h peak 2
Rank²	#6,292	top 28%
Last wipe	27d ago	no schedule published
Next wipe³	–	too few wipes 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.

AveragePeak

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 28% 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: too few wipes seen yet

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

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Wipe-day peak	1	players, last three wipes

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Fri 2 Oct, 10:2027d ago	1	–	running	0

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 5: The map: Procedural Map.

Table 4: The server's published settings.

Address	`125.254.123.81:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	2 Oct 2026, 10:20 UTC
Hostname	–
First seen	13 Sep 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 next Rust wipe times [3].

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

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 151 on average	156/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	125/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	190/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average	102/700
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average	237/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 84 on average	348/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Relics Dev Server based?

A region is not published by Relics Dev Server. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 125.254.123.81:28015 is its address.

A.2What is the online status and reliability of Relics Dev Server?

Relics Dev Server is currently online. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. Its first appearance in Rust Statistics's records is 13 September 2026.

A.3What version of Rust is run on Relics Dev Server?

Relics Dev Server is running Rust network protocol 2635 and build 168909 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4When are wipes carried out on Relics Dev Server?

There are not yet enough recorded wipes for Relics Dev Server to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 27 days 7 hours ago.

A.5What characterises wipe day on Relics Dev Server?

The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 3 hours after it began.

Player count

A.6How does Relics Dev Server compare with other Rust servers in the rankings?

Ranked by player hours across seven days, Relics Dev Server holds #6,292, in the top 28% of all ranked servers.

A.7How would you characterise the player activity on Relics Dev Server?

At this moment 1 players are on Relics Dev Server, which has 10 slots in total. Averaged over the last seven days: 0 players; the same period peaks at 2. Averaging 1 players, 12:00 UTC was the busiest hour of the past 48.

Tags and filters

A.8What is the meaning of the tags on Relics Dev Server?

gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): It offers 10 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags Relics Dev Server publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Relics Dev Server be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Relics Dev Server: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.10Which settings and rules are in force on Relics Dev Server?

No gather rate appears in the name of Relics Dev Server. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

A.11What is the map for Relics Dev Server?

A procedural map, generated by the game, is what Relics Dev Server runs.

Connection

A.12How do you connect to Relics Dev Server?

Press F1 inside Rust to open the console and enter client.connect 125.254.123.81:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

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

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp10`	Max players. It offers 10 slots.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2635`	Protocol. Joining requires the same game version: protocol 2635.
`cs168909`	Build. This server runs game build 168909.
`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. Oxide (uMod), a plugin framework, runs on this server.
`^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. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.