Offline 169.58.222.85:28015 checked 10d ago
RomaxaCoders Server
Connect
srv = rust.server("169.58.222.85: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, measured since 23 Sep. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 17h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 17h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:00 UTC FW27d ago | 2 | 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
3000 · seed 1337
- map
- Procedural Map
- size
- 3000
- seed
- 1337
Server
srv.info()- address
- 169.58.222.85:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 21:00 UTC
- hostname
- –
- first seen
- 23 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 565 on average | 198/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 123/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 24/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 289 on average | 11/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 23/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 29/225 |
Quick answers
From the figures on this page.
Population data
How does RomaxaCoders Server compare in the rankings?
Over the last seven days RomaxaCoders Server sits at #15,316 on player hours, in the top 70% of ranked servers.
How many players does RomaxaCoders Server hold at once?
Offline now for RomaxaCoders Server, with the last sample 10 days 14 hours ago.
Server facts
Which Rust version is RomaxaCoders Server on?
Rust network protocol 2634 and build 166494 on Linux is what RomaxaCoders Server runs. Steam updates your game for you, but the protocol must match to join.
Is RomaxaCoders Server up, and what does its uptime show?
RomaxaCoders Server is offline at this refresh; the last response came 10 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 23 September 2026.
In which location is RomaxaCoders Server hosted?
No region is published by RomaxaCoders Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 169.58.222.85:28015.
Settings and map
What rules and settings are recorded for RomaxaCoders Server?
You will not find a gather rate in the string RomaxaCoders Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.
Which map has RomaxaCoders Server loaded?
RomaxaCoders Server runs a procedural map of size 3,000 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does RomaxaCoders Server wipe, and how often?
The only wipe RomaxaCoders Server takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 27 days 4 hours ago, and that is the one in play.
What is wipe day on RomaxaCoders Server like?
Recent wipes averaged 2 players at their peak. The crowd on the latest wipe topped out 23 hours after it began.
Tags and filters
Which lists on Rust Data hold RomaxaCoders Server, and which filters?
On Rust Data, RomaxaCoders Server appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on RomaxaCoders Server hold?
These tags are published by RomaxaCoders Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join RomaxaCoders Server?
In Rust, F1 opens the console: type client.connect 169.58.222.85:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.