Offline 5.231.119.253:28015 checked 5d ago
Rust Update Check
Connect
srv = rust.server("5.231.119.253: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 50% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 23:07 UTC5d 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
- 5.231.119.253:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 22 Oct 2026, 23:07 UTC
- hostname
- –
- first seen
- 22 Oct 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 · 155 on average | 145/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 171/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 86/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 38/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Rust Update Check take in the server rankings?
Player hours over seven days put Rust Update Check at #11,045, in the top 50% of the ranked set.
How full does Rust Update Check run?
The current row shows Rust Update Check offline; the last response was 5 days 9 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What is the Rust version on Rust Update Check?
Rust network protocol 2635 and build 168909 on Windows is what Rust Update Check runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Rust Update Check, and is it online now?
Offline now for Rust Update Check, last seen 5 days 9 hours ago. Over the last 5 full days the hours up number 0 of 120, 0%. Its earliest recorded date in Rust Data is 22 October 2026.
Where does Rust Update Check sit?
No region is published by Rust Update Check. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 5.231.119.253:28015 is its address.
Settings and map
Which rules apply on Rust Update Check, and what settings?
The name Rust Update Check carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is not running; Valve's anti-cheat is off.
Which map has Rust Update Check selected?
A procedural map runs on Rust Update Check, generated by the game.
Wipe data
When does Rust Update Check wipe, and how often?
The record for Rust Update Check 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. This world was created 5 days 9 hours ago.
On Rust Update Check, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does Rust Update Check appear among Rust Data lists and filters?
On Rust Data, Rust Update Check appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on Rust Update Check hold?
The game's server browser reads these tags from Rust Update Check: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. 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.
Connecting
What is the way to join Rust Update Check?
In Rust, F1 opens the console: type client.connect 5.231.119.253:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.