Rust Server Analytics 69,594 players11,814 servers
All servers
Drill-through Server detail

reseT

Offline 91.121.43.194:26975 checked 9d ago

Drill-through
FilterServeris reseT
Attributes
monthly wipes vanillamoddedoxide
Last refreshed
Players now 1/ 5
7-day average 0 peak –
Rank #13,995 top 64%
Last wipe 9d ago monthly schedule
Next wipe 7d 5h Thu 5 Nov, 19:00 UTC FW
Capacity 20% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 64% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. The force wipe · high confidence

usual gap1.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

Coming wipes

InWhen, UTCKind
7d 5hThu 5 Nov, 19:00 UTCFW force wipe
35d 5hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Tue 20 OctWed 14 OctSat 3 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 11:21 UTC9d ago 1 – running 0
Wed 14 Oct, 18:58 UTC14d ago 0 – 5.7 days 0
Sat 3 Oct, 10:46 UTC26d ago 1 halved by day 1 11.3 days 0
Fri 2 Oct, 22:27 UTC26d ago 1 – 0.5 days 0
Thu 1 Oct, 14:46 UTC27d ago 1 – 1.3 days 0
Tue 29 Sep, 08:36 UTC30d ago 1 – 2.3 days 1
Mon 28 Sep, 21:22 UTC30d ago 1 – 0.5 days 1
Mon 28 Sep, 11:03 UTC31d ago 1 – 0.4 days 1
Wed 23 Sep, 10:52 UTC36d ago 1 – 5 days 1
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average 75 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 27 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 84 on average 251 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 EU · groups of 16+ · monthly · 73 on average 107 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 EU · groups of 16+ · monthly · 67 on average 16 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 EU · groups of 16+ · monthly · 66 on average 404 / 1000

Quick answers

from the figures on this page

Wipe data

When does reseT wipe?

The force wipe is the only wipe for reseT, once a month. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. The current world dates from 9 days 1 hours. Its tags state a wipe schedule of one month.

On reseT, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population for the latest wipe came 0 hours after it began. Above half that peak until the next wipe held in 0% of recent wipes. The fall below half arrived by day 1 when it didn't hold.

Server

Which location hosts reseT?

A region is not published by reseT. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 91.121.43.194:26975.

What Rust build does reseT run?

Rust network protocol 2634 and build 167781 on Linux is the setup for reseT. Your game must match the protocol to join, and Steam applies that update.

How reliable is reseT, and is it online now?

The current status is offline for reseT, with the last sighting 9 days 1 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0%. 13 September 2026 is when Rust Server Analytics first recorded it.

Tags

How should the tags on reseT be read?

The game's server browser reads the tags reseT publishes: gmrust (Game mode): Survival in the standard Rust format; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): To join, your game version must match protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^v (Vanilla): Facepunch's game unchanged: no altered rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

Where does reseT appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include reseT: Modded Rust servers: live data. It appears on the server list under the following filters: 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.

Population

Where does reseT sit among Rust servers?

On player hours over seven days, reseT ranks #13,995, within the top 64% of ranked servers.

How many players does reseT carry?

The last sighting of reseT was 9 days 1 hours ago; it is offline at this refresh.

Settings

How is reseT configured, and what rules apply?

No gather rate is given in the name of reseT. The default group cap of 8 players applies. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. Vanilla is its own description: facepunch's game unchanged: no altered rates, kits or rules. VAC, Valve's anti-cheat, is enabled.

What is the map for reseT?

reseT uses a procedural map of size 4,000 with seed 1, generated by the game. Size and seed fix the map, so a RustMaps view is available from this page. The name of the map is Custom Map.

How to join

How do you connect to reseT?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 91.121.43.194:26975.

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,^m,^v,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, the stock game setting.
v2634
Protocol To join, your game version must match protocol 2634.
cs167781
Build Game build: 167781.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Wipe schedule

^m
Monthly A monthly cycle, with Facepunch's force wipe as the reset.

Difficulty

^v
Vanilla Facepunch's game unchanged: no altered rates, kits or rules.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section, because plugins or settings modify play.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.