Element card · group Modded · atomic number 6,640, its rank
PukekoLabs Battlefield
Online NA 147.135.4.144:28015 checked 1h ago
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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
Top 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
- 6d 6hWed 4 Nov, 00:16 UTC
- 8d 0hThu 5 Nov, 19:00 UTCFW
- 13d 6hWed 11 Nov, 00:16 UTC
- 20d 6hWed 18 Nov, 00:16 UTC
- 27d 6hWed 25 Nov, 00:16 UTC
- 34d 6hWed 2 Dec, 00:16 UTC
- 36d 0hThu 3 Dec, 19:00 UTCFW
- 41d 6hWed 9 Dec, 00:16 UTC
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 wipesQuick answers
from the figures on this pageMap and rules
What map is in play on PukekoLabs Battlefield?
PukekoLabs Battlefield runs a procedural map of size 2,000 with seed 3211; the game generates it. You can view it on RustMaps from this page, since matching size and seed produce the same map.
What settings and rules apply on PukekoLabs Battlefield?
The name of PukekoLabs Battlefield carries no gather rate. Groups top out at 8 players, the default for the game. battlefield is the game mode, quick PvP, kits and high rates included. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running on it. VAC is on, Valve's anti-cheat.
Server details
Which location is PukekoLabs Battlefield based in?
The NA tag is how PukekoLabs Battlefield lists itself, in North America. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 147.135.4.144:28015.
On what Rust version does PukekoLabs Battlefield operate?
Rust network protocol 2635 and build 168909 on Linux is what PukekoLabs Battlefield uses. Joining requires the same protocol on your game; Steam takes care of updating it.
How reliably does PukekoLabs Battlefield stay online?
PukekoLabs Battlefield is live as of now. About 5 days 14 hours ago is when it last restarted, based on its uptime. It was online for 168 of 168 hours in the last 7 full days, which is 100% uptime. The first sighting by Rust Data Lab was on 3 October 2026.
How well does PukekoLabs Battlefield perform?
The last 48 hours show an average of 45 server fps and a minimum of 34. Buildings, deployables and everything else in the world added up to as many as 31,109 entities. Memory use peaked at 2,272 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.
Wipes and resets
When does PukekoLabs Battlefield wipe, and how often?
Following the tag is the best the prediction can do for PukekoLabs Battlefield, whose record holds too few wipes to confirm its schedule. On Wednesday 4 November at 00:16 UTC the next wipe falls due. The world it is running now dates from 7 days 16 hours ago. Weekly wipes are what its tags advertise.
What does a typical wipe day on PukekoLabs Battlefield involve?
Recent wipes on average reached 2 players at their busiest. 3 hours after the latest wipe, the crowd peaked.
Tags, lists
What should you understand from the tags PukekoLabs Battlefield carries?
The game's server browser reads the tags PukekoLabs Battlefield publishes, which are gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): 100 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): No region code is set; ^w (Weekly): It wipes weekly; ^i (Battlefield): High rates and kits for quick PvP; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): Because plugins or settings change the game, it is filed under Modded; NA (North America): In the browser it sits under North America. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.
Where among the Rust Data Lab lists and filters does PukekoLabs Battlefield come up?
These themed Rust Data Lab lists carry PukekoLabs Battlefield: Modded Rust servers, measured, Battlefield servers, measured and North American Rust servers: the sample. 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.
Player counts
Against other Rust servers, where does PukekoLabs Battlefield place?
Seven-day player hours place PukekoLabs Battlefield at #6,640 overall, #1,043 in North America and in the top 30% of ranked servers.
What does the current player count on PukekoLabs Battlefield tell you?
At the moment PukekoLabs Battlefield has 0 of its 100 slots filled. The week's figures average 0 players and top out at 2. The busiest point in the last 48 hours came at 21:00 UTC, averaging 2 players.
How to join
What steps get you onto PukekoLabs Battlefield?
In Rust, press F1 and enter client.connect 147.135.4.144:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.