Online 125.254.123.81:28015 checked 8m ago
Relics Dev Server
Connect
srv = rust.server("125.254.123.81:28017")
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 27% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:20 UTC27d ago | 1 | NaN | 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. 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.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
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 · 149 on average | 35/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 63/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 20/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 60/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 256/310 |
Quick answers
From the figures on this page.
Population
How does Relics Dev Server compare in the rankings?
Player hours over seven days put Relics Dev Server at #5,999, in the top 27% of the ranked set.
What population does Relics Dev Server carry?
Current row: 0 players on Relics Dev Server, against 10 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 12:00 UTC is the busiest, at 1 players.
About the server
Which Rust version is Relics Dev Server on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by Relics Dev Server. Steam updates your game for you, but the protocol must match to join.
How reliable is Relics Dev Server, and is it online now?
Online is the state at the latest refresh for Relics Dev Server. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does Relics Dev Server run from?
No region is published by Relics Dev Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 125.254.123.81:28015 is its address.
Rules, settings, map
What rules and settings are recorded for Relics Dev Server?
No gather rate appears in the name: Relics Dev Server. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Relics Dev Server loaded?
The game generates its map: procedural, on Relics Dev Server.
Wipes and dates
When does Relics Dev Server wipe, and on what schedule?
The record for Relics Dev Server holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 27 days 12 hours ago.
On Relics Dev Server, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 3 hours in.
Tags, lists
Which lists on Rust Data hold Relics Dev Server, and which filters?
These Rust Data lists include Relics Dev Server: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Relics Dev Server hold?
These tags are published by Relics Dev Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into Relics Dev Server?
The manual route: launch Rust, F1, then client.connect 125.254.123.81:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.