Rust StatisticsWorking papers on every public Rust server · 54,666 players now

theBATCAVE

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 17d ago · 69.27.68.164:28015

Abstract

We describe the public Rust server theBATCAVE, reached at 69.27.68.164:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,800 of all servers, the top 72%. It last wiped 26d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmonthly wipes modded oxide pve

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/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,800top 72%
Last wipe26d agomonthly schedule
Next wipe37d 19hThu 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.

4Rank

The server stands in the top 72% 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 Sep26 Sep1 Oct7 Oct12 Oct18 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 19h. 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 19hforce wipefw
Thu 3 Dec, 19:0035d 19hforce 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
Fri 2 Oct, 16:0326d 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

No map picture published
Figure 5: The map: Procedural Map.
Table 5: The server's published settings.
Address69.27.68.164:28015
Region–
Max players10
Group limit8, the default
Wipe schedulemonthly
Last wipe2 Oct 2026, 16:03 UTC
Hostname–
First seen13 Sep 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 servers by player count [2], live pve population [3] and Rust wipe forecast [4].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 53 on average62/300
[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 51 on average57/200
[US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 39 on average34/200
1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 35 on average18/200
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼EA · groups of 8+ · monthly · 35 on average2/100
Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average40/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is theBATCAVE based?

There is no region published for theBATCAVE. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 69.27.68.164:28015.

A.2What is the reliability of theBATCAVE, and is it online?

Right now, theBATCAVE is offline, and the last time it was seen was 17 days 9 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.

A.3What is the Rust version for theBATCAVE?

Rust network protocol 2634 and build 167398 is the version that theBATCAVE runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4When are wipes carried out on theBATCAVE?

The only wipe for theBATCAVE is the monthly force wipe. This server's next wipe coincides with the force wipe on Thursday 5 November at 19:00 UTC, which affects all Rust servers. The world currently in use was created 26 days 7 hours ago. The tags show that the server wipes monthly.

A.5What happens on theBATCAVE when wipe day arrives?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6What position does theBATCAVE occupy in the ranking of Rust servers?

Ranked by player hours across seven days, theBATCAVE holds #15,800, in the top 72% of all ranked servers.

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

The last recorded sighting of theBATCAVE was 17 days 9 hours ago; it is offline now.

Tags, lists

A.8What do the tags associated with theBATCAVE signify?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167398 (Build): Build 167398 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^m (Monthly): A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe; ^p (PvE): There is no player combat; the world supplies the danger; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game, which theBATCAVE publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

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

Modded Rust servers and Rust PvE servers: live list are the Rust Statistics lists that theBATCAVE fits. These filters on the server list return it: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Rules, settings, map

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

Its name carries no gather rate for theBATCAVE. At 8 players, the group limit equals the game's default. Listed as pve, the game mode is fighting other players is excluded. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.11On which map does theBATCAVE take place?

On theBATCAVE the terrain is procedural, built by the game itself.

How to join

A.12How do you connect to theBATCAVE?

Press F1 inside Rust to open the console and enter client.connect 69.27.68.164:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2634,^m,^p,gmrust,cs167398,ts8,^o^z.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp10Max players. 10 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs167398Build. Build 167398 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. The region code is unset.
Wipe schedule
^mMonthly. A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe.
Gameplay
^pPvE. There is no player combat; the world supplies the danger.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. Modded listing: plugins or settings modify the game.

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 servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Live pve population. ruststatistics.org/top-rust-pve-servers.
  4. [4]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.