Offline 2.27.5.157:28015 checked 2d ago
Rust Update Check
Connect
srv = rust.server("2.27.5.157: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 46% 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 | Sun 25 Oct, 16:01 UTC2d 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 2.27.5.157:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 17:24 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 · 163 on average | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 61/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 | 17/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Rust Update Check take in the server rankings?
Rank #10,319 on seven-day player hours for Rust Update Check, within the top 46% of all ranked servers.
How many players does Rust Update Check hold at once?
Rust Update Check returns no live count at this refresh, having last been seen 2 days 6 hours ago. Over the last seven days it averaged 1 players and peaked at 1.
About the server
What Rust version does Rust Update Check run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Rust Update Check. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Rust Update Check, and is it up?
Offline now for Rust Update Check, last seen 2 days 6 hours ago. Over the last 1 full day the hours up number 0 of 24, 0%. Its earliest recorded date in Rust Data is 25 October 2026.
In which location is Rust Update Check hosted?
No region is published by Rust Update Check. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 2.27.5.157:28015 is its address.
Map and rules
Which rules apply on Rust Update Check, and what settings?
The name Rust Update Check carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, 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: Carbon. Anti-cheat status: VAC off.
Wipe schedule
When does Rust Update Check wipe, and on what schedule?
The record for Rust Update Check 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. This world was created 2 days 6 hours ago.
On Rust Update Check, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold Rust Update Check, and which filters?
On Rust Data, Rust Update Check appears in these lists: 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 3 days.
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): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is 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.
Join steps
What is the way into Rust Update Check?
In Rust, F1 opens the console: type client.connect 2.27.5.157:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.