Rust StatisticsWorking papers on every public Rust server · 73,784 players now

SOLO FRONTIER | BR OUTPOST 3500 | TEST

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 7d ago · 95.182.105.168:28115

Abstract

We describe the public Rust server SOLO FRONTIER | BR OUTPOST 3500 | TEST, reached at 95.182.105.168:28115. It is offline at the last check, against a seven-day mean of 01. It ranks #15,957 of all servers, the top 70%. It last wiped 7d ago.

Keywordsrust server

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/50% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,957top 70%
Last wipe7d agono schedule published
Next wipe3–too few wipes seen yet

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.

4Rank

The server stands in the top 70% 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
15k10k15k20k28 Oct29 Oct31 Oct1 Nov3 Nov4 Nov
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
00.250.50.751+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 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 28 Oct, 11:277d ago 1 – 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

Custom map, no picture published
Figure 5: The map: Custom Map.
Table 4: The server's published settings.
Address95.182.105.168:28115
Region–
Max players5
Group limit8, the default
Wipe schedule–
Last wipe28 Oct 2026, 12:29 UTC
Hostname–
First seen28 Oct 2026
MapCustom Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are community tab servers measured [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - BR MainSA · groups of 16+ · weekly · 161 on average24/250
ARENA BR SOLO | VANILLA | LATAM | SOLO ONLYSA · groups of 8+ · biweekly · 61 on average28/200
[LATAM] Sudamerica United | 29/10 WipeSA · groups of 32+ · monthly · 48 on average3/200
[BR] CLT Rustico SOLO/DUO Full Wipe [29/10]SA · groups of 8+ · biweekly · 23 on average7/150
[BR/LATAM] Rust Na Veia | MAX 4 |SA · groups of 8+ · weekly · 17 on average3/200
[BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 30/10SA · groups of 8+ · weekly · 14 on average0/300

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does SOLO FRONTIER | BR OUTPOST 3500 | TEST have?

Its name points to South America, though SOLO FRONTIER | BR OUTPOST 3500 | TEST publishes no region tag. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 95.182.105.168:28115.

A.2What is the online status and reliability of SOLO FRONTIER | BR OUTPOST 3500 | TEST?

At the present moment, SOLO FRONTIER | BR OUTPOST 3500 | TEST is offline; it was last seen 7 days 1 hours ago. Its uptime over the last full days (6 days) was 0%, with 0 of 144 hours online. Its first appearance in Rust Statistics's records is 28 October 2026.

A.3What is the Rust version for SOLO FRONTIER | BR OUTPOST 3500 | TEST?

The version of Rust on SOLO FRONTIER | BR OUTPOST 3500 | TEST is network protocol 2635 and build 168909, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4When are wipes carried out on SOLO FRONTIER | BR OUTPOST 3500 | TEST?

Too few wipes by SOLO FRONTIER | BR OUTPOST 3500 | TEST have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 7 days 3 hours ago.

A.5How would you describe wipe day on SOLO FRONTIER | BR OUTPOST 3500 | TEST?

Recent wipes saw an average peak of 1 players. The peak on the latest wipe came 0 hours after it began.

Player count

A.6How does SOLO FRONTIER | BR OUTPOST 3500 | TEST compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts SOLO FRONTIER | BR OUTPOST 3500 | TEST at #15,957, within the top 70% of ranked servers.

A.7What is the population level of SOLO FRONTIER | BR OUTPOST 3500 | TEST?

At this moment SOLO FRONTIER | BR OUTPOST 3500 | TEST is offline, having last been seen 7 days 1 hours ago. The mean population for the last seven days is 0.

Tags and filters

A.8How should the tags on SOLO FRONTIER | BR OUTPOST 3500 | TEST be interpreted?

Tags from SOLO FRONTIER | BR OUTPOST 3500 | TEST, read by the game's server browser, are gmrust (Game mode): Rust survival, in its standard form; mp5 (Max players): It offers 5 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can SOLO FRONTIER | BR OUTPOST 3500 | TEST be found among the Rust Statistics lists and filters?

These Rust Statistics lists include SOLO FRONTIER | BR OUTPOST 3500 | TEST: Rust community servers, measured. It appears under the following filters on the server list: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.10What are the settings and rules that govern SOLO FRONTIER | BR OUTPOST 3500 | TEST?

Its name carries no gather rate for SOLO FRONTIER | BR OUTPOST 3500 | TEST. At 8 players, the group limit equals the game's default. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. Community is its category in the server browser. VAC, Valve's anti-cheat, is enabled.

Connection

A.11How do you connect to SOLO FRONTIER | BR OUTPOST 3500 | TEST?

Enter client.connect 95.182.105.168:28115 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 mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp5Max players. It offers 5 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. This server runs game build 168909.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.

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. Community tab servers measured. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.