Offline 31.173.170.141:28015 checked 2d ago
Rust Update Check
Connect
srv = rust.server("31.173.170.141: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 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 4, 9 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 07:31 UTC2d ago | 4 | NaN | running | 0 |
| 1 | Sun 25 Oct, 17:24 UTC3d ago | 4 | NaN | 0.6 days | 1 |
| 2 | Thu 22 Oct, 23:07 UTC6d ago | 1 | NaN | 2.8 days | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 31.173.170.141:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 07:31 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 · 150 on average | 74/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 112/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 40/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 12/1000 |
Quick answers
From the figures on this page.
Population data
How does Rust Update Check compare in the rankings?
Over the last seven days Rust Update Check sits at #5,240 on player hours, in the top 24% of ranked servers.
What population does Rust Update Check carry?
The current row shows Rust Update Check offline; the last response was 2 days 12 hours ago. Over the last seven days it averaged 2 players and peaked at 4.
Server data
Which Rust version is Rust Update Check on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Rust Update Check. 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 2 days 12 hours ago. Uptime of 15% across the last 6 full days: 22 hours of 144. Its earliest recorded date in Rust Data is 22 October 2026.
Which location does Rust Update Check run from?
No region is published by Rust Update Check. Rust Data does not look up where the machine stands; it shows where a server says it is. 31.173.170.141:28015 is its address.
Map and rules
What rules and settings are recorded for Rust Update Check?
You will not find a gather rate in the string Rust Update Check. The group limit sits at the default of 8 players. 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. The plugin count is Carbon. The VAC field reads off.
Wipe data
On what schedule does Rust Update Check wipe?
Irregular wipe times on Rust Update Check leave no next wipe to forecast. 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 2 days 23 hours ago.
What is wipe day on Rust Update Check like?
Across recent wipes the busiest point averaged 3 players. Peak population on the latest wipe came 9 hours in.
Lists and tags
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. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on Rust Update Check?
These tags are published by Rust Update Check and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Rust Update Check?
In Rust, F1 opens the console: type client.connect 31.173.170.141:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.