Fig. 1Players on reseTRG-S13995-01 · Sheet 1 of 10
Fig. 2
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S13995-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 64% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S13995-03 · Sheet 3 of 10
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h.
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
6d 21hThu 5 Nov, 19:00 UTCFW
34d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Tue 20 OctWed 14 OctSat 3 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ScheduleExpected wipesRG-S13995-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 20 Oct, 11:21 UTC9d ago
1
–
running
0
Wed 14 Oct, 18:58 UTC15d 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 UTC28d ago
1
–
1.3 days
0
Tue 29 Sep, 08:36 UTC30d ago
1
–
2.3 days
1
Mon 28 Sep, 21:22 UTC31d 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 UTC42d 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.
Table 1Wipe logRG-S13995-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
The current state of reseT is offline, with the last sighting 9 days 9 hours ago. For the last 7 full days the record is 0 of 168 hours up, 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
What location is recorded for reseT?
No region is published by reseT. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 91.121.43.194:26975.
3.
What Rust version is recorded for reseT?
On Linux, reseT runs Rust network protocol 2634 and build 167781. Steam updates your game, which must be on the same protocol for you to join.
Player data
4.
How many players are plotted on reseT?
The latest refresh records reseT as offline, last seen 9 days 9 hours ago.
5.
In the rankings, which position does reseT hold?
Player hours over seven days place reseT at #13,995, within the top 64% of ranked servers.
Wipe data
6.
On reseT, what does the data show for wipe day?
An average of 1 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. On the wipes where it did not hold, the crowd dropped below half by day 1.
7.
On reseT, when do wipes occur?
At reseT the only wipe is the monthly force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 9 days 10 hours ago. The tags state a wipe schedule of one wipe a month.
Map and rules
8.
Which settings does reseT run, and what rules?
No gather rate is stated in the name of reseT. No limit is published beyond the default: 8 players per group. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings change the game. The plugin count is Oxide. Vanilla is the label it uses: facepunch's game, unaltered: rates, kits and rules are as shipped. Anti-cheat: VAC, from Valve, is on.
9.
What is the map for reseT?
Size 4,000 with seed 1: that is the procedural map reseT runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.
Filters
10.
On Rust Graphs, which lists and filters contain reseT?
On Rust Graphs, reseT is placed in these lists: Modded Rust servers. It is returned by these filters 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.
11.
Which meaning is attached to each tag on reseT?
The game's server browser reads these tags from reseT: gmrust (Game mode): Standard survival, as Rust plays; mp5 (Max players): 5 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): 167781 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Joining the server
12.
How is reseT joined?
In Rust, press F1 and type client.connect 91.121.43.194:26975 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
NotesAnswered from the figuresRG-S13995-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,^m,^v,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeStandard survival, as Rust plays.
mp5
Max players5 player slots.
ts8
Group limitTeams are capped at 8, the default setting.
v2634
ProtocolJoin only if your game is on protocol 2634.
cs167781
Build167781 is the game build.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Wipe schedule
^m
MonthlyMonthly wipes, on Facepunch's force wipe.
Difficulty
^v
VanillaFacepunch's game, unaltered: rates, kits and rules are as shipped.
Mods and access
^o
OxideThe plugin framework is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
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.
KeyTag string decodedRG-S13995-10 · Sheet 10 of 10
