Offline 23.94.252.8:28015 checked 1d ago
Rust Update Check
Connect
srv = rust.server("23.94.252.8: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, measured since 26 Oct. 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
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
3500 · seed 481516
- map
- Custom Map
- size
- 3500
- seed
- 481516
Server
srv.info()- address
- 23.94.252.8:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 17:24 UTC
- hostname
- –
- first seen
- 26 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 · 162 on average | 35/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.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 · 114 on average | 50/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 39/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 7/200 |
| 5 | CSL Scenery Budget Test | groups of 8+ · 85 on average | 0/500 |
Quick answers
From the figures on this page.
Population data
What position does Rust Update Check take in the server rankings?
Rank #11,102 on seven-day player hours for Rust Update Check, within the top 50% of all ranked servers.
What population does Rust Update Check carry?
The current row shows Rust Update Check offline; the last response was 42 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 07:00 UTC is the busiest, at 1 players.
Server facts
How well does Rust Update Check perform?
Server fps over the last 48 hours averages 129; the floor is 111. The entity count peaked at 56,715, covering buildings, deployables and the rest of the world. The memory field tops out at 1,977 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Rust Update Check on?
Rust network protocol 2635 and build 168909 on Windows is what Rust Update Check runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Rust Update Check, and is it up?
Rust Update Check is offline at this refresh; the last response came 42 hours ago. The uptime it reports puts the last restart about 1 hours ago. Uptime of 0% across the last 1 full day: 0 hours of 24. The first row Rust Data holds for it is dated 26 October 2026.
Where does Rust Update Check sit?
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. You can reach it at 23.94.252.8:28015.
Map and rules
Which rules apply on Rust Update Check, and what settings?
No gather rate appears in the name: Rust Update Check. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. The VAC field reads off.
Which map has Rust Update Check selected?
Rust Update Check runs a procedural map of size 3,500 with seed 481516, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipe data
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 7 hours ago.
Tags and filters
Where does Rust Update Check appear among Rust Data lists and filters?
The Rust Data lists that Rust Update Check fits are: 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.
How should you read the server tags on Rust Update Check?
Read by the game's server browser, the tags Rust Update Check publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to Rust Update Check?
In Rust, F1 opens the console: type client.connect 23.94.252.8:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.