Online 160.251.143.180:28015 checked 13m ago
hitosetserver001
Connect
srv = rust.server("160.251.143.180: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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 18 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 20:59 UTC FW27d ago | 1 | 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
5000 · seed 244772856
- map
- Procedural Map
- size
- 5000
- seed
- 244772856
Server
srv.info()- address
- 160.251.143.180:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 20:59 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 188/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 72/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 208/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 349/350 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does hitosetserver001 rank?
Rank #15,289 on seven-day player hours for hitosetserver001, within the top 69% of all ranked servers.
What population does hitosetserver001 carry?
Current row: 0 players on hitosetserver001, against 10 slots. Over the last seven days it averaged 0 players.
About the server
What does performance look like on hitosetserver001?
The 48-hour average is 49 server fps, with a low of 31. Buildings, deployables and all else in the world took the count as high as 154,763 entities. The memory field tops out at 5,415 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on hitosetserver001?
The build is Rust network protocol 2634 and build 166586 on Linux, run by hitosetserver001. Joining needs the same protocol on your game; Steam handles the update.
How reliable is hitosetserver001, and is it online now?
Online is the state at the latest refresh for hitosetserver001. The uptime it reports puts the last restart about 5 days 19 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is hitosetserver001 hosted?
For hitosetserver001, 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. 160.251.143.180:28015 is its address.
Map and rules
What rules and settings are recorded for hitosetserver001?
You will not find a gather rate in the string hitosetserver001. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has hitosetserver001 loaded?
Size 5,000, seed 244772856: the procedural map on hitosetserver001, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does hitosetserver001 wipe, and on what schedule?
A single wipe each month, the force wipe, is all hitosetserver001 does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 27 days 22 hours ago.
What is wipe day on hitosetserver001 like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 18 hours in.
Tags and filters
Which lists on Rust Data hold hitosetserver001, and which filters?
On Rust Data, hitosetserver001 appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on hitosetserver001?
The game's server browser reads these tags from hitosetserver001: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): The server runs build 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. 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 hitosetserver001?
The manual route: launch Rust, F1, then client.connect 160.251.143.180:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.