Offline 1.46.153.173:28015 checked 32d ago
RUST UNTIMATE.RATE
Connect
srv = rust.server("1.46.153.173:28016")
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 best
Top 68% 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, 25 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 09:15 UTC33d ago | 1 | NaN | running | 1 |
# 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
- 1.46.153.173:28015
- region
- –
- max players
- 6
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 10:50 UTC
- hostname
- –
- first seen
- 24 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 · 163 on average | 74/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 84/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 31/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 77/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17/1000 |
Quick answers
From the figures on this page.
Population
How does RUST UNTIMATE.RATE compare in the rankings?
Over the last seven days RUST UNTIMATE.RATE sits at #15,591 on player hours, in the top 68% of ranked servers.
How full does RUST UNTIMATE.RATE run?
RUST UNTIMATE.RATE returns no live count at this refresh, having last been seen 32 days 12 hours ago.
Server data
What Rust version does RUST UNTIMATE.RATE run?
Version Rust network protocol 2633 and build 162929 on Windows is reported by RUST UNTIMATE.RATE. The protocol has to match before you can join, and Steam does the updating.
How reliable is RUST UNTIMATE.RATE, and is it online now?
Offline now for RUST UNTIMATE.RATE, last seen 32 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 24 September 2026.
Which location does RUST UNTIMATE.RATE run from?
There is no region published for RUST UNTIMATE.RATE. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 1.46.153.173:28015.
Rules, settings, map
Which rules apply on RUST UNTIMATE.RATE, and what settings?
No gather rate appears in the name: RUST UNTIMATE.RATE. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on RUST UNTIMATE.RATE?
The game generates its map: procedural, on RUST UNTIMATE.RATE.
Wipes and dates
When does RUST UNTIMATE.RATE wipe, and on what schedule?
The record for RUST UNTIMATE.RATE 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 33 days 12 hours ago, and that is the one in play.
What is wipe day on RUST UNTIMATE.RATE like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 25 hours after it began.
Tags, lists
Which Rust Data filters and lists contain RUST UNTIMATE.RATE?
On Rust Data, RUST UNTIMATE.RATE appears in these lists: 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 RUST UNTIMATE.RATE hold?
These tags are published by RUST UNTIMATE.RATE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp6 (Max players): 6 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Build number: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to RUST UNTIMATE.RATE?
In Rust, F1 opens the console: type client.connect 1.46.153.173:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.