Statistical profileOffline
SOLO FRONTIER | BR OUTPOST 3500 | TEST
95.182.105.168:28115 checked 7d ago
Connect to this server
1. Main points
Players now
0/ 5
0% full
7-day average
0
peak –
Rank
#15,957
top 70%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 5 slots.
- It ranks #15,957 of all ranked servers, the top 70%, on player hours over the last seven days.
- Its current map went up 7d ago.
2. Players
Figure 1: Players on SOLO FRONTIER | BR OUTPOST 3500 | TEST
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players 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.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 11:27 UTC7d ago | 1 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of SOLO FRONTIER | BR OUTPOST 3500 | TEST
Table 2: The world
As the server publishes it
| Map | Custom Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of SOLO FRONTIER | BR OUTPOST 3500 | TEST
What the server publishes and what was recorded
| Address | 95.182.105.168:28115 |
|---|---|
| Region | – |
| Max players | 5 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 28 Oct 2026, 12:29 UTC |
| Hostname | – |
| First seen | 28 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rustoria.co - BR Main | SA · groups of 16+ · weekly · 161 on average | 40 / 250 |
| ARENA BR SOLO | VANILLA | LATAM | SOLO ONLY | SA · groups of 8+ · biweekly · 62 on average | 27 / 200 |
| [LATAM] Sudamerica United | 29/10 Wipe | SA · groups of 32+ · monthly · 47 on average | 5 / 200 |
| [BR] CLT Rustico SOLO/DUO Full Wipe [29/10] | SA · groups of 8+ · biweekly · 23 on average | 8 / 150 |
| [BR/LATAM] Rust Na Veia | MAX 4 | | SA · groups of 8+ · weekly · 17 on average | 0 / 200 |
| [BR/LATAM] ORIGEMZ | VANILLA | SOLO/DUO/TRIO | WIPE 30/10 | SA · groups of 8+ · weekly · 14 on average | 0 / 300 |
10. Quick answers
From the figures on this page.
Wipe records
This release records the wipe timetable for SOLO FRONTIER | BR OUTPOST 3500 | TEST: what is it?
With too few wipes of SOLO FRONTIER | BR OUTPOST 3500 | TEST on record, its rhythm remains unclear. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. This world was generated 7 days 5 hours ago.
How is wipe day run on SOLO FRONTIER | BR OUTPOST 3500 | TEST?
Recent wipes drew an average peak of 1 players. On the latest wipe, 0 hours passed before the crowd peaked.
Server record
What does the record show for the uptime and current status of SOLO FRONTIER | BR OUTPOST 3500 | TEST?
The latest count records SOLO FRONTIER | BR OUTPOST 3500 | TEST as offline, last seen 7 days 3 hours ago. 0 of 144 hours on across the last 6 full days gives an uptime of 0%. First recorded by Rust Census on 28 October 2026.
Which location does SOLO FRONTIER | BR OUTPOST 3500 | TEST run from?
Pointing to South America is SOLO FRONTIER | BR OUTPOST 3500 | TEST's name, though no region tag is published. Rust Census does not look up where the machine stands; it shows where a server says it is. At 95.182.105.168:28115 it is addressed.
Which Rust version is SOLO FRONTIER | BR OUTPOST 3500 | TEST running?
This release lists SOLO FRONTIER | BR OUTPOST 3500 | TEST on Rust network protocol 2635 and build 168909, running on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Player figures
What are the current player figures for SOLO FRONTIER | BR OUTPOST 3500 | TEST?
SOLO FRONTIER | BR OUTPOST 3500 | TEST is offline at present; its last recording was 7 days 3 hours ago. The seven-day average for this server is 0 players.
In the rankings of Rust servers, where is SOLO FRONTIER | BR OUTPOST 3500 | TEST placed?
For seven-day player hours, SOLO FRONTIER | BR OUTPOST 3500 | TEST is ranked #15,957, placing it in the top 70% of all ranked servers.
Tag details
Which Rust Census filters and lists cover SOLO FRONTIER | BR OUTPOST 3500 | TEST?
Included in these Rust Census lists is SOLO FRONTIER | BR OUTPOST 3500 | TEST: Community servers. It appears under these 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.
Which meanings do the tags on SOLO FRONTIER | BR OUTPOST 3500 | TEST carry?
gmrust (Game mode): Survival play, in the standard Rust format; mp5 (Max players): Slots: 5; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): The server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code are the tags SOLO FRONTIER | BR OUTPOST 3500 | TEST publishes, and the game's server browser reads them. At the top of this page you will find the tags for current players, queue and world creation time.
Map and rules
How is SOLO FRONTIER | BR OUTPOST 3500 | TEST configured, and what rules does it keep?
The name of SOLO FRONTIER | BR OUTPOST 3500 | TEST carries no gather rate. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Community is its section in the server browser. The server runs VAC, Valve's anti-cheat.
Connecting
How can you connect to SOLO FRONTIER | BR OUTPOST 3500 | TEST?
Enter client.connect 95.182.105.168:28115 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp5 | Max players Slots: 5. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2635 | Protocol Protocol 2635 is required; a different version cannot join. |
cs168909 | Build The server runs game build 168909. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code This server carries no region code. |
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.