Rust StatisticsWorking papers on every public Rust server · 97,045 players now

PukekoLabs Battlefield

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 26d ago · 147.135.4.144:28015

Abstract

We describe the public Rust server PukekoLabs Battlefield, reached at 147.135.4.144:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,958 of all servers, the top 70%. It last wiped 26d 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/400% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,958top 70%
Last wipe26d 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
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 Oct
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
Usual gap1.3 daysbetween real wipes
Wipe-day peak0players, last three wipes
Sat 3 OctThu 1 Oct
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
Sat 3 Oct, 03:3326d ago 0 – running 0
Thu 1 Oct, 20:32fw27d ago 0 – 1.3 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.
Address147.135.4.144:28015
Region–
Max players40
Group limit8, the default
Wipe schedule–
Last wipe3 Oct 2026, 03:33 UTC
Hostname–
First seen20 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 rust battlefield servers [2], busiest community rust servers [3] and next Rust wipe times [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
【极光】100000000倍|枪战|礼包|建造|新手入门EA · groups of 16+ · 19 on average31/200
【星云】10000倍|爆枪|秒造|全解|礼包|新手入门EA · groups of 16+ · 15 on average0/200
ADRENALIN Rust RU 2X [ лутай СКИНЫ ] Loot+EU · groups of 60+ · 2x · weekly · 4 on average3/100
RUSTBURG.GG #1〔X5/X10|NO LIMIT|LOOT+|FPS+|KITS|TP〕27.10EU · groups of 50+ · 5x · weekly · 184 on average280/275
Scrapland x10000000 |BATTLEFIELD|KITS|TP|CLANS|SKINBOX|PVP|NA · groups of 35+ · 1e+07x · weekly · 139 on average76/100
CoolingLine #1 - x1000 | NOLIMIT | FAST | LOOT+ | FPS |CLANSEU · groups of 100+ · 1000x · weekly · 63 on average157/165

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does PukekoLabs Battlefield have?

A region is not published by PukekoLabs Battlefield. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 147.135.4.144:28015.

A.2What is the online status and reliability of PukekoLabs Battlefield?

Right now, PukekoLabs Battlefield is offline, and the last time it was seen was 26 days 12 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. It was first observed on 20 September 2026 by Rust Statistics.

A.3What version of Rust is run on PukekoLabs Battlefield?

The version of Rust on PukekoLabs Battlefield is network protocol 2634 and build 166652, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does PukekoLabs Battlefield follow for wipes?

There are not yet enough recorded wipes for PukekoLabs Battlefield to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The current world has been running for 26 days 12 hours.

A.5What characterises wipe day on PukekoLabs Battlefield?

Recent wipes saw an average peak of 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6How does PukekoLabs Battlefield compare with other Rust servers in the rankings?

Ranked by player hours across seven days, PukekoLabs Battlefield holds #15,958, in the top 70% of all ranked servers.

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

The last recorded sighting of PukekoLabs Battlefield was 26 days 12 hours ago; it is offline now.

Tags, lists

A.8What do the tags associated with PukekoLabs Battlefield signify?

gmrust (Game mode): Survival on standard Rust rules; mp40 (Max players): It offers 40 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166652 (Build): Build 166652 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset: these are the tags PukekoLabs Battlefield publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

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

Rust battlefield servers and Rust community servers, measured are the Rust Statistics lists that PukekoLabs Battlefield fits. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.10Which settings and rules are in force on PukekoLabs Battlefield?

The name of PukekoLabs Battlefield states no gather rate. The group cap is 8 players, which is the default in the game. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. It is a community server, as the browser's Community listing shows. VAC is active: that is Valve's anti-cheat.

A.11What is the map for PukekoLabs Battlefield?

On PukekoLabs Battlefield the terrain is procedural, built by the game itself.

Connection

A.12What is the process for joining PukekoLabs Battlefield?

Press F1 inside Rust to open the console and enter client.connect 147.135.4.144: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 mp40,ptrak,$r?,v2634,gmrust,cs166652,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp40Max players. It offers 40 slots.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs166652Build. Build 166652 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.

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