ArmA 3 Ports Explained (2302–2306 UDP)

Q: Egg mapping?

Egg 19 uses `-port={{SERVER_PORT}}`. Successive +1..+4 services follow that base — copy the base from Pterodactyl.

ArmA 3 dedicated servers use a base game port (wiki 2302/UDP) plus contiguous Steam/BattlEye ports. Chapter22 egg 19 sets -port={{SERVER_PORT}}.

Port table

Service	Port	Protocol	Public?
Game	SERVER_PORT (wiki 2302)	UDP	Yes — players
Steam query	Base +1 (wiki 2303)	UDP	Yes — browser
Steam	Base +2 (wiki 2304)	UDP	Yes
VON (reserved)	Base +3 (wiki 2305)	UDP	Typically reserved
BattlEye	Base +4 (wiki 2306)	UDP	Yes if BE enabled

Managed hosting (Chapter22)

Open Pterodactyl → ArmA 3 server.
Copy primary SERVER_PORT allocation.
Expect query/Steam/BE to use base+1…+4 — confirm Network allocations span that range.
Share game IP:port for Direct Connect; browser uses query (base+1).

VERIFY panel allocation span. Node has 2302–2310 available for provisioning.

DIY / self-hosted readers

DIY: open 2302–2306/UDP (or your remapped span). See Linux ports.

Egg verification (Chapter22)

Egg 19 (Arma 3): -port={{SERVER_PORT}}; open SERVER_PORT through +4/UDP typical. Node has 2302-2310 unassigned. HC_NUM 0-5 supported on egg.

Headless clients

Egg 19 exposes HC_NUM (0–5). See the Headless Client guide.

Frequently Asked Questions

Default range?

BI docs: game 2302/UDP, query 2303, Steam 2304, VON 2305, BattlEye 2306 — typically open 2302–2306/UDP.

Egg mapping?

Egg 19 uses -port={{SERVER_PORT}}. Successive +1..+4 services follow that base — copy the base from Pterodactyl.

Node pool?

Chapter22 node currently has 2302–2310 unassigned — good span for ArmA stacks when provisioned.

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.