Rust StatisticsWorking papers on every public Rust server · 93,889 players now

rust-sim private probe probe_1000_1

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 18d ago · 81.196.141.3:28115

Abstract

We describe the public Rust server rust-sim private probe probe_1000_1, reached at 81.196.141.3:28115. It is offline at the last check, against a seven-day mean of 01. It ranks #16,964 of all servers, the top 70%. It last wiped 18d ago.

Keywordsmodded carbon

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/10% full
In the queue0no queue
Seven-day mean0peak –
Rank2#16,964top 70%
Last wipe18d agono schedule published
Next wipe3–no rhythm it keeps

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
15k10k15k20k30 Oct1 Nov3 Nov5 Nov7 Nov9 Nov
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.6 daysbetween real wipes
On rhythm67%of its recent wipes
Wipe-day peak0players, last three wipes
Mon 2 NovMon 2 NovSun 1 Nov
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 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 5 Nov, 19:00fw15d ago – – running –
Mon 2 Nov, 21:3918d ago 0 – – 0
Mon 2 Nov, 10:3619d ago 0 – 0.5 d 0
Sun 1 Nov, 18:2919d ago 0 – 0.7 d 0
Sun 1 Nov, 04:2720d ago 0 – 0.6 d 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

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address81.196.141.3:28115
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe2 Nov 2026, 21:39 UTC
Hostname–
First seen30 Oct 2026
MapProcedural 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 modded server list with rates [2] and Rust wipe forecast [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
МИНИ-КАРТА 2Х | STORM | FPS+ 21.11EU · groups of 8+ · weekly · 128 on average132/100
ShockRust | Blue | NoLimitno group limit · 110 on average288/400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11EU · groups of 16+ · weekly · 98 on average190/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11EU · groups of 16+ · monthly · 79 on average78/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11EU · groups of 16+ · monthly · 68 on average128/1000
ShockRust | Green | MAX 4no group limit · 65 on average135/250

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of rust-sim private probe probe_1000_1?

No region is published by rust-sim private probe probe_1000_1. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 81.196.141.3:28115.

A.2What is the reliability of rust-sim private probe probe_1000_1, and is it online?

At the present moment, rust-sim private probe probe_1000_1 is offline; it was last seen 18 days 17 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. The first record of it by Rust Statistics dates to 30 October 2026.

A.3What is the Rust version for rust-sim private probe probe_1000_1?

rust-sim private probe probe_1000_1 is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4When are wipes carried out on rust-sim private probe probe_1000_1?

No next wipe can be predicted for rust-sim private probe probe_1000_1 since its wipes occur at irregular intervals. The monthly force wipe takes place on Thursday 3 December at 19:00 UTC and clears all Rust servers. The current world has been running for 18 days 17 hours.

A.5How would you describe wipe day on rust-sim private probe probe_1000_1?

Across its recent wipes, the average peak population was 0 players. The peak on the latest wipe came 0 hours after it began.

Population

A.6What position does rust-sim private probe probe_1000_1 occupy in the ranking of Rust servers?

Ranked by player hours across seven days, rust-sim private probe probe_1000_1 holds #16,964, in the top 70% of all ranked servers.

A.7What is the population level of rust-sim private probe probe_1000_1?

At this moment rust-sim private probe probe_1000_1 is offline, having last been seen 18 days 17 hours ago.

Tags and filters

A.8What do the tags associated with rust-sim private probe probe_1000_1 signify?

gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): 1 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): Plugins run through Carbon: these are the tags rust-sim private probe probe_1000_1 publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can rust-sim private probe probe_1000_1 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that rust-sim private probe probe_1000_1 fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Rules, settings, map

A.10Which settings and rules are in force on rust-sim private probe probe_1000_1?

The name of rust-sim private probe probe_1000_1 states no gather rate. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is gather, build and raid: the standard game. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Carbon on this server. The server has VAC on, Valve's anti-cheat.

A.11What is the map for rust-sim private probe probe_1000_1?

On rust-sim private probe probe_1000_1 the terrain is procedural, built by the game itself.

Connection

A.12What is the process for joining rust-sim private probe probe_1000_1?

Enter client.connect 81.196.141.3: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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp1Max players. 1 slots are available.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. Build 168909 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
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. Plugins run through Carbon.

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 server list with rates. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.