Online 160.251.250.29:28015 checked 30m ago
RustServer_2626
Connect
srv = rust.server("160.251.250.29: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 17 Sep. 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 best
Top 69% 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 3, 19 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 19:13 UTC21d ago | 3 | NaN | running | 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
3000 · seed 2011
- map
- Procedural Map
- size
- 3000
- seed
- 2011
Server
srv.info()- address
- 160.251.250.29:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 19:13 UTC
- hostname
- –
- first seen
- 13 Sep 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 495 on average | 84/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 397/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 21/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 476/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 362/425 |
Quick answers
From the figures on this page.
Population data
What position does RustServer_2626 take in the server rankings?
Rank #15,262 on seven-day player hours for RustServer_2626, within the top 69% of all ranked servers.
How full does RustServer_2626 run?
Current row: 0 players on RustServer_2626, against 50 slots. Over the last seven days it averaged 0 players.
About the server
How smoothly does RustServer_2626 run?
The 48-hour average is 133 server fps, with a low of 104. The entity count peaked at 46,707, covering buildings, deployables and the rest of the world. A high of 2,378 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on RustServer_2626?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_2626 runs. The protocol has to match before you can join, and Steam does the updating.
Is RustServer_2626 up, and what does its uptime show?
The current sample puts RustServer_2626 online. A restart about 6 days 1 hours ago is what its reported uptime implies. Uptime of 85% across the last 7 full days: 143 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does RustServer_2626 sit?
For RustServer_2626, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 160.251.250.29:28015.
Map and rules
Which rules apply on RustServer_2626, and what settings?
No gather rate appears in the name: RustServer_2626. 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. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
What is the map on RustServer_2626?
The game generates the map on RustServer_2626: procedural, size 3,000, seed 2011. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does RustServer_2626 wipe?
Too few wipes are on record for RustServer_2626 to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 21 days 5 hours ago.
On RustServer_2626, what happens on wipe day?
The average peak over recent wipes is 3 players. Peak population on the latest wipe came 19 hours in.
Tags and filters
Where does RustServer_2626 appear among Rust Data lists and filters?
The Rust Data lists that RustServer_2626 fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on RustServer_2626 hold?
The game's server browser reads these tags from RustServer_2626: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to RustServer_2626?
In Rust, F1 opens the console: type client.connect 160.251.250.29:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.