Offline 77.83.246.150:28015 checked 3d ago
Rust Update Check
Connect
srv = rust.server("77.83.246.150: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 63% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 77.83.246.150:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 17:08 UTC
- hostname
- –
- first seen
- 25 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 | 29/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 30/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 92 on average | 22/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Rust Update Check rank?
Player hours over seven days put Rust Update Check at #14,057, in the top 63% of the ranked set.
How many players does Rust Update Check hold at once?
Offline now for Rust Update Check, with the last sample 3 days 8 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
Server facts
What Rust version does Rust Update Check run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Rust Update Check. The protocol has to match before you can join, and Steam does the updating.
How reliable is Rust Update Check, and is it up?
Offline now for Rust Update Check, last seen 3 days 8 hours ago. Uptime of 0% across the last 3 full days: 0 hours of 72. Rust Data logged it first on 25 October 2026.
Where does Rust Update Check sit?
For Rust Update Check, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 77.83.246.150:28015.
Settings and map
What rules and settings are recorded for Rust Update Check?
The name Rust Update Check carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. The VAC field reads off.
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. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 8 hours ago.
Tags, lists
Which lists on Rust Data hold Rust Update Check, and which filters?
These Rust Data lists include Rust Update Check: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
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): Slot count: 10; 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): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Rust Update Check?
The manual route: launch Rust, F1, then client.connect 77.83.246.150:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.