Rust StatisticsWorking papers on every public Rust server · 66,169 players now

Anderssons challenge

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 7d ago · 158.174.102.177:28023

Abstract

We describe the public Rust server Anderssons challenge, reached at 158.174.102.177:28023. It is offline at the last check, against a seven-day mean of 01. It ranks #15,349 of all servers, the top 69%. It last wiped 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/40% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,349top 69%
Last wipe27d agono schedule published
Next wipe37d 6hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak0players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:007d 6hforce wipefw
Thu 3 Dec, 19:0035d 6hforce wipefw
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 19:11fw27d ago 0 – 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Anderssons challenge
Figure 5: The map: Procedural Map, size 3500, seed 1939034539. Open on RustMaps.
Table 5: The server's published settings.
Address158.174.102.177:28023
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 19:11 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3500
Seed1939034539

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and upcoming Rust wipes [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 149 on average166/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average181/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average71/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average13/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average21/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Anderssons challenge based?

No region is published by Anderssons challenge. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 158.174.102.177:28023 is its address.

A.2What is the online status and reliability of Anderssons challenge?

Right now, Anderssons challenge is offline, and the last time it was seen was 7 days 7 hours ago. Its uptime over the last full days (7 days) was 3%, with 5 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.3What is the Rust version for Anderssons challenge?

Rust network protocol 2634 and build 166586 is the version that Anderssons challenge runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does Anderssons challenge follow for wipes?

The only wipe for Anderssons challenge is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. The world currently in use was created 27 days 17 hours ago.

A.5What characterises wipe day on Anderssons challenge?

Across its recent wipes, the average peak population was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6What is the rank of Anderssons challenge among Rust servers?

The seven-day player-hours ranking puts Anderssons challenge at #15,349, within the top 69% of ranked servers.

A.7How would you characterise the player activity on Anderssons challenge?

At this moment Anderssons challenge is offline, having last been seen 7 days 7 hours ago. The seven-day average for this server is 0 players.

Tags, lists

A.8How should the tags on Anderssons challenge be interpreted?

gmrust (Game mode): Rust survival, in its standard form; mp4 (Max players): The slot count is 4; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166586 (Build): Build 166586 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags Anderssons challenge publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Anderssons challenge be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Anderssons challenge fits. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.10What are the settings and rules that govern Anderssons challenge?

Its name carries no gather rate for Anderssons challenge. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.

A.11What is the map for Anderssons challenge?

The game generates Anderssons challenge's procedural map at size 3,500, from seed 1939034539. Because size and seed determine the map, RustMaps can show it, linked from this page.

Connection

A.12What steps are required to join Anderssons challenge?

Enter client.connect 158.174.102.177:28023 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp4,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp4Max players. The slot count is 4.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166586Build. Build 166586 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.