Offline 1.46.48.220:28015 checked 41d ago
RUST UNTIMATE.RATE
Connect
srv = rust.server("1.46.48.220: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 bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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. 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 1.46.48.220:28015
- region
- –
- max players
- 6
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Sep 2026, 04:57 UTC
- hostname
- –
- first seen
- 16 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 | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 67/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 58/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 15/1000 |
Quick answers
From the figures on this page.
Population
How does RUST UNTIMATE.RATE compare in the rankings?
Player hours over seven days put RUST UNTIMATE.RATE at #13,349, in the top – of the ranked set.
What population does RUST UNTIMATE.RATE carry?
RUST UNTIMATE.RATE returns no live count at this refresh, having last been seen 41 days 13 hours ago.
Server facts
What Rust version does RUST UNTIMATE.RATE run?
The build is Rust network protocol 2633 and build 162929 on Windows, run by RUST UNTIMATE.RATE. Steam updates your game for you, but the protocol must match to join.
How reliable is RUST UNTIMATE.RATE, and is it up?
The latest sample has RUST UNTIMATE.RATE offline, with a last sighting 41 days 13 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 16 September 2026.
Which location does RUST UNTIMATE.RATE run from?
There is no region published for RUST UNTIMATE.RATE. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 1.46.48.220:28015.
Settings and map
What rules and settings are recorded for RUST UNTIMATE.RATE?
No gather rate appears in the name: RUST UNTIMATE.RATE. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Wipe data
On what schedule does RUST UNTIMATE.RATE wipe?
Too few wipes are on record for RUST UNTIMATE.RATE to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 41 days 19 hours ago.
Lists and tags
Which Rust Data filters and lists contain RUST UNTIMATE.RATE?
On Rust Data, RUST UNTIMATE.RATE appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on RUST UNTIMATE.RATE?
The game's server browser reads these tags from RUST UNTIMATE.RATE: 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): To join, your game must run protocol 2633; cs162929 (Build): The server runs build 162929; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^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
What is the way to join RUST UNTIMATE.RATE?
Enter client.connect 1.46.48.220:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.