On the class lists: D (53), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average0peak 2
Rank#6,622top 30% · #1039 in NA
Last wipe7d agoweekly schedule
Next wipe6d 2hWed 4 Nov, 00:16 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
70/ 100
B−
Holds a respectable place: #6,622 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
74/ 100
B−
Slows down under load at times: 45 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
48/ 100
D
Slipped a little: down 302 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in uptime (A); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 30% of all ranked servers, top 56% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Wednesday 4 November, 00:16 UTC, in 6d 2h.
Its weekly schedule tag · low confidence
wipe-day peak2players, last three wipes
Coming wipes
6d 2hWed 4 Nov, 00:16 UTC
7d 20hThu 5 Nov, 19:00 UTCFW
13d 2hWed 11 Nov, 00:16 UTC
20d 2hWed 18 Nov, 00:16 UTC
27d 2hWed 25 Nov, 00:16 UTC
34d 2hWed 2 Dec, 00:16 UTC
35d 20hThu 3 Dec, 19:00 UTCFW
41d 2hWed 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
classmates: the same kind of game, then region, group limit, rate and wipes
The NA tag on PukekoLabs Battlefield puts it in North America. Rust Server Score takes the server's word for its location and does not trace the hardware. 147.135.4.144:28015 is the address to use.
How reliable is PukekoLabs Battlefield, and is it up?
You can join now: PukekoLabs Battlefield is online. According to its reported uptime, the last restart was about 5 days 18 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
How well does PukekoLabs Battlefield run?
The average over the last 48 hours was 45 server fps, and it never went below 34. Buildings, deployables and everything else in the world added up to as many as 31,109 entities. Memory use reached up to 2,272 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is PukekoLabs Battlefield running?
The server PukekoLabs Battlefield is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does PukekoLabs Battlefield wipe its map?
The prediction follows its tag, because too few of PukekoLabs Battlefield's wipes are on record to confirm the schedule. It is due to wipe next on Wednesday 4 November at 00:16 UTC. The world it runs now was created 7 days 20 hours. Wipes are scheduled weekly, according to its tags.
What happens on PukekoLabs Battlefield when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 3 hours into the latest wipe.
Population
Where does PukekoLabs Battlefield sit among Rust servers?
In North America, PukekoLabs Battlefield is #1,039, and overall it is #6,622 on player hours over the last seven days, in the top 30% of all ranked servers.
How many players does PukekoLabs Battlefield usually have?
PukekoLabs Battlefield is showing 1 players right now, with 100 slots in total. It peaked at 2 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 21:00 UTC, with an average of 2 players.
Lists and filters
How should you read the tags on PukekoLabs Battlefield?
The game's browser takes its cue from the tags PukekoLabs Battlefield has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^i (Battlefield): High rates and kits keep the PvP fast; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): You will find it under North America in the browser. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does PukekoLabs Battlefield appear in the Rust Server Score lists and filters?
Rust Server Score lists that include PukekoLabs Battlefield: Modded Rust servers, graded, Rust battlefield servers, graded and North America Rust servers, graded. 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.
Rules and settings
Which rules does PukekoLabs Battlefield enforce, and what are its settings?
Nothing in the name of PukekoLabs Battlefield states a gather rate. The group limit stays at the game's default of 8 players. It runs battlefield, high rates and kits, for fast PvP. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map PukekoLabs Battlefield uses?
A procedural map of size 2,000 and seed 3211, generated by the game, is what PukekoLabs Battlefield runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
What is the way to join PukekoLabs Battlefield?
Enter client.connect 147.135.4.144:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^i,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Gameplay
^i
BattlefieldHigh rates and kits keep the PvP fast.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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.
A fair term, with more to come. Strongest in uptime (A); population is the one to work on (F).