Open every day, at every hour Admission free 11,888 servers and 103,775 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 15,958Acc. 2026.15958

PukekoLabs Battlefield

Rust server · in the archive since 20 September 2026

Offline 147.135.4.144:28015 checked 26d ago

To visit
Players now 0/ 40
0% full
7-day average0peak –
Rank#15,958top 70%
Last wipe26d agoSat 3 Oct, 03:33 UTC · no schedule published
Next wipe–too few wipes seen yet

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectedlast seen, 3 Oct 2026, 03:33 UTCAll times UTC.

The record of each wipe

  1. Sat 3 Oct 202603:33 UTC26d ago
    Peak
    0
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 1 Oct 202620:32 UTC FW27d ago
    Peak
    0
    Crowd
    –
    Lasted
    1.3 days
    Players before
    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. A new world less than six hours after a wipe is a restart, not a wipe of its own.

The rhythm

Wipe schedule

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.

1.3 daysusual gapbetween real wipes
0wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

Sat 3 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Folder 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Folder 3

Rank

RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Lists and tags

What do the server tags on PukekoLabs Battlefield mean?

You can see the tags PukekoLabs Battlefield publishes, read by the game's server browser: gmrust (Game mode): This server runs standard Rust survival; mp40 (Max players): Slot count: 40; ts8 (Group limit): The game default caps teams at 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): No region code is set. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

Which Rust Server History lists and filters include PukekoLabs Battlefield?

These Rust Server History lists include PukekoLabs Battlefield: Rust battlefield servers and Rust community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

The record

Which version of Rust does PukekoLabs Battlefield run?

Rust network protocol 2634 and build 166652 is the build PukekoLabs Battlefield runs, on Linux. Joining requires your game to be on the same protocol; Steam keeps it updated for you.

Is PukekoLabs Battlefield online, and how reliable is it?

Offline now, PukekoLabs Battlefield was last seen 26 days 14 hours ago. 0 of 168 hours, or 0% of the time, over the last 7 full days. First seen by Rust Server History on 20 September 2026.

Where is PukekoLabs Battlefield located?

No region is published by PukekoLabs Battlefield. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. Its entry gives 147.135.4.144:28015 as the address.

Wipe log

What does wipe day look like on PukekoLabs Battlefield?

An average peak of 0 players was drawn by its recent wipes. At 0 hours after the latest wipe, the crowd reached its peak.

What is the wipe schedule on PukekoLabs Battlefield?

The record holds too few of PukekoLabs Battlefield's wipes to tell its rhythm. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. The world it runs now dates from 26 days 14 hours ago.

Player record

How does PukekoLabs Battlefield rank against other Rust servers?

Over seven days of player hours, PukekoLabs Battlefield ranks #15,958, inside the top 70% of all ranked servers.

How busy is PukekoLabs Battlefield?

No current count exists for PukekoLabs Battlefield; it was last seen 26 days 14 hours ago.

Rules, map

What are the rules and settings on PukekoLabs Battlefield?

No gather rate is stated in the name of PukekoLabs Battlefield. At 8 players, the group limit matches the game's default. Under game mode, the entry reads survival, gathering, building and raiding: the standard game. PvP and raiding are enabled. The server browser lists it under Community, as a community server. VAC from Valve is switched on.

Which map does PukekoLabs Battlefield run?

A procedural map is what PukekoLabs Battlefield runs; the game generates it.

How to join

How do I join PukekoLabs Battlefield?

Enter client.connect 147.135.4.144:28015 in the console, opened with F1 in Rust. Launch Rust and join on this page also works: it opens Rust through Steam and connects you.

The label explained

Server tags

What each tag this server publishes means.

Published as mp40,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode This server runs standard Rust survival.
mp40
Max players Slot count: 40.
ts8
Group limit The game default caps teams at 8.
v2634
Protocol To join, your game has to be on protocol 2634.
cs166652
Build Build number: 166652.
ptrak
Networking RakNet handles the network layer, as standard for 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.