PukekoLabs Battlefield
Online NA 147.135.4.144:28015 checked 1h ago
Server instruments
last reading Wed 16:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 34 · below 20 is lag, below 10 is badEntities
48 h range 25,675–31,109 · memory 2,184 MBUptime
5 days 14 hours since its last restart, at the last readingPlayers
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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 30% of all ranked servers, top 56% in NA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Wednesday 4 November, 00:16 UTC, in 6d 6h. Its weekly schedule tag · low confidence
Coming wipes
- WPT 1Wed 4 Nov, 00:16 UTC6d 6h
- WPT 2Thu 5 Nov, 19:00 UTC8d 0hFW
- WPT 3Wed 11 Nov, 00:16 UTC13d 6h
- WPT 4Wed 18 Nov, 00:16 UTC20d 6h
- WPT 5Wed 25 Nov, 00:16 UTC27d 6h
- WPT 6Wed 2 Dec, 00:16 UTC34d 6h
- WPT 7Thu 3 Dec, 19:00 UTC36d 0hFW
- WPT 8Wed 9 Dec, 00:16 UTC41d 6h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 3 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 00:16 UTC7d ago | 2 | – | running | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 70/100
- 9/200
- 2/100
- 0/200
- 0/200
- 2/50
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on PukekoLabs Battlefield?
An average of 2 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 3 hours in.
How often does PukekoLabs Battlefield wipe, and when?
The prediction follows its tag, because too few of PukekoLabs Battlefield's wipes are on record to confirm its schedule. Due on Wednesday 4 November at 00:16 UTC is its next wipe. 7 days 16 hours ago the current world was made. A weekly wipe schedule is published in its tags.
Tags
How should you read the tags on PukekoLabs Battlefield?
Tags published by PukekoLabs Battlefield, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): Check: wipe cycle. Every week; ^i (Battlefield): Kits and high rates feed fast PvP here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; NA (North America): Its browser listing: North America. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does PukekoLabs Battlefield appear in Rust Metrics lists and filters?
On Rust Metrics, PukekoLabs Battlefield sits in these lists: Modded Rust servers, checked live, Rust battlefield servers: check the readings and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Occupancy
What position does PukekoLabs Battlefield hold among Rust servers?
Top 30% of all ranked servers: PukekoLabs Battlefield takes #6,640 on seven-day player hours and #1,043 in North America.
How full does PukekoLabs Battlefield get?
0 of 100 slots are filled on PukekoLabs Battlefield right now. Check: players over seven days. Average 0, peak 2. The last 48 hours peaked at 21:00 UTC, averaging 2 players at that hour.
Operator and location
Which location does PukekoLabs Battlefield run from?
Reading: location. The NA tag puts PukekoLabs Battlefield in North America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 147.135.4.144:28015.
What Rust version is PukekoLabs Battlefield on?
Rust network protocol 2635 and build 168909 on Linux is the build PukekoLabs Battlefield runs. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for PukekoLabs Battlefield?
Check: fps. Average 45 server fps over the last 48 hours, low of 34. Within range. Check: entities. The peak was 31,109, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 2,272 MB. Expect lag when fps falls and entities climb.
Is PukekoLabs Battlefield up, and how often does it stay up?
Check: connection. PukekoLabs Battlefield is online at this moment. Check: restart. The uptime it reports puts the last restart about 5 days 14 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 3 October 2026, recorded by Rust Metrics.
Map and rules
What rules does PukekoLabs Battlefield enforce, and what are its settings?
No gather rate appears in the name: PukekoLabs Battlefield. No limit is set beyond the default. Groups take up to 8 players. battlefield, high rates and kits for fast PvP — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
Which map is live on PukekoLabs Battlefield?
Check: map. Procedural, size 2,000, seed 3211, generated by the game on PukekoLabs Battlefield. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How do you connect to PukekoLabs Battlefield?
Press F1 in Rust and enter client.connect 147.135.4.144:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.