Offline 91.121.43.194:26975 checked 9d ago
reseT
Connect
srv = rust.server("91.121.43.194:26978")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 64% 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 7d 5h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 5h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 5h | 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 11:21 UTC9d ago | 1 | NaN | running | 0 |
| 1 | Wed 14 Oct, 18:58 UTC14d ago | 0 | NaN | 5.7 days | 0 |
| 2 | Sat 3 Oct, 10:46 UTC26d ago | 1 | halved by day 1 | 11.3 days | 0 |
| 3 | Fri 2 Oct, 22:27 UTC26d ago | 1 | NaN | 0.5 days | 0 |
| 4 | Thu 1 Oct, 14:46 UTC27d ago | 1 | NaN | 1.3 days | 0 |
| 5 | Tue 29 Sep, 08:36 UTC30d ago | 1 | NaN | 2.3 days | 1 |
| 6 | Mon 28 Sep, 21:22 UTC30d ago | 1 | NaN | 0.5 days | 1 |
| 7 | Mon 28 Sep, 11:03 UTC31d ago | 1 | NaN | 0.4 days | 1 |
| 8 | Wed 23 Sep, 10:52 UTC36d ago | 1 | NaN | 5 days | 1 |
| 9 | Thu 17 Sep, 15:01 UTC41d ago | 1 | halved by day 1 | 5.8 days | 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
4000 · seed 1
- map
- Custom Map
- size
- 4000
- seed
- 1
Server
srv.info()- address
- 91.121.43.194:26975
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 20 Oct 2026, 11:21 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 86/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 28/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 265/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 73 on average | 109/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 67 on average | 20/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 66 on average | 411/1000 |
Quick answers
From the figures on this page.
Population data
How does reseT compare in the rankings?
Player hours over seven days put reseT at #13,995, in the top 64% of the ranked set.
How full does reseT run?
The current row shows reseT offline; the last response was 9 days 1 hours ago.
Server data
Which Rust version is reseT on?
The build is Rust network protocol 2634 and build 167781 on Linux, run by reseT. Joining needs the same protocol on your game; Steam handles the update.
How reliable is reseT, and is it online now?
Offline now for reseT, last seen 9 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does reseT sit?
No region is published by reseT. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 91.121.43.194:26975.
Map and rules
Which rules apply on reseT, and what settings?
No gather rate appears in the name: reseT. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. VAC is running: Valve's anti-cheat is on.
Which map has reseT loaded?
reseT runs a procedural map of size 4,000 with seed 1, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.
Wipe schedule
When does reseT wipe, and how often?
A single wipe each month, the force wipe, is all reseT does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 9 days 2 hours ago. Its tags carry a monthly wipe schedule.
On reseT, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.
Lists and tags
Which Rust Data filters and lists contain reseT?
These Rust Data lists include reseT: Modded Rust servers. These filters bring it up on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
Which meanings do the tags on reseT hold?
The game's server browser reads these tags from reseT: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join reseT?
In Rust, F1 opens the console: type client.connect 91.121.43.194:26975. Launch Rust on this page does the same by opening the game through Steam and connecting.