Station XX-15958 · no signal
PukekoLabs Battlefield
Offline 147.135.4.144:28015 checked 26d ago
- Players now
- 0/ 40
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,958
- top 70%
- Last wipe
- 26d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 40 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1.3 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 03:33 UTC26d ago | M0.0■steady | 0 | – | – | running | 0 |
| Thu 1 Oct, 20:32 UTC FW27d ago | M0.0■steady | 0 | – | 1.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on PukekoLabs Battlefield?
The map on PukekoLabs Battlefield is procedural, produced by the game.
Which settings and rules apply on PukekoLabs Battlefield?
You will find no gather rate in the name of PukekoLabs Battlefield. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Under Community in the server browser, it runs as a community server. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on PukekoLabs Battlefield?
No players are recorded on PukekoLabs Battlefield at this moment; it is offline, and the last sighting was 26 days 15 hours ago.
How does PukekoLabs Battlefield rank against other Rust servers?
The last seven days of player hours place PukekoLabs Battlefield at #15,958, in the top 70% of all ranked servers.
Server facts
How reliably does PukekoLabs Battlefield stay online?
No contact with PukekoLabs Battlefield right now, and the last recorded contact was 26 days 15 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 20 September 2026.
Which region does PukekoLabs Battlefield run from?
A region is not published by PukekoLabs Battlefield. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 147.135.4.144:28015.
What build of Rust does PukekoLabs Battlefield use?
Rust network protocol 2634 and build 166652 on Linux is what PukekoLabs Battlefield runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on PukekoLabs Battlefield?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does PukekoLabs Battlefield run its wipes?
The rhythm of PukekoLabs Battlefield cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 26 days 15 hours.
Server tags
What do the server tags on PukekoLabs Battlefield mean?
Tags published by PukekoLabs Battlefield and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does PukekoLabs Battlefield appear?
You will find PukekoLabs Battlefield on the following Rust Server Trends lists: Rust battlefield servers and Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Connecting
How do you connect to PukekoLabs Battlefield?
To join, enter client.connect 147.135.4.144:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.