Squad is a 100-player military simulation that bridges the gap between arcade shooters and full-blown milsim. Teams of 50 coordinate across squads to capture objectives, build forward operating bases, and deploy vehicles ranging from logistics trucks to main battle tanks. Running a Squad server is more involved than most games because of the hardware demands and the licensing process, but the payoff is a tight-knit community that plays on your terms.
System requirements
- RAM: 8 to 16 GB. A full 100-player server with vehicles and heavy combat uses 12 to 14 GB consistently. Budget 16 GB to avoid out-of-memory crashes during peak fights.
- CPU: 4 to 6 cores. Squad's server is one of the most CPU-hungry game servers around. Single-thread performance is critical for tick rate stability.
- Storage: 25 to 30 GB for the server files. Maps are large and updates are frequent.
- Network: Port 7787 UDP (game), 27165 UDP (Steam query), and 21114 TCP (RCON). Bandwidth requirements are significant at 100 players.
The AMD Ryzen 9 7950X in HostValues servers is one of the strongest choices for Squad. Its per-core performance keeps the tick rate above 30 even during large firefights. DDoS protection is included on all plans, which matters for a game with competitive communities.
OWI server licensing
Offworld Industries (the developer) requires a free license for servers that appear in the public browser. Apply through their website with your server name, IP, and a brief description of your community. Unlicensed servers still work for private use but will not be listed publicly. The process typically takes a few days.
Installation
- Install SteamCMD on your VPS or select Squad in the HostValues game panel.
- Download the server:
app_update 403240 validate. This is a large download (20+ GB). - Open ports 7787 UDP, 27165 UDP, and 21114 TCP.
- Edit configuration files in
SquadGame/ServerConfig/before first launch. - Start the server:
./SquadGameServer.shon Linux.
Server configuration
Main configuration files:
- Server.cfg: Server name, password, max players, tick rate, and game rules.
- Admins.cfg: Steam IDs of administrators and their permission levels.
- MapRotation.cfg: The map and layer rotation. Each map has multiple "layers" with different vehicle loadouts, team sizes, and objectives.
- Rcon.cfg: Remote console password and settings for external admin tools.
Map layers explained
Squad maps come in layers. The same map (like Yehorivka or Gorodok) has multiple versions: AAS (Advance and Secure), RAAS (Randomized AAS), Invasion, TC (Territory Control), and Skirmish. Each layer has a different vehicle pool, team composition, and point layout. A well-curated layer rotation keeps gameplay varied without repeating the same experience.
Admin tools and RCON
Squad supports RCON for remote administration. Popular tools:
- SquadJS: A community-built Node.js framework for plugins, auto-messages, team balancing, and logging. Most serious Squad servers run SquadJS for its automatic team scramble, map vote, and seeding features.
- BattleMetrics: External RCON panel with player tracking, bans, and server stats. Integrates with SquadJS for a complete admin toolchain.
At minimum, assign admins who can kick, ban, and switch maps. Active administration is expected by the Squad community. Unmoderated servers lose population quickly because team balance and fair play depend on admin presence.
Building a community
Squad servers live and die by their community. A server without regulars empties out during off-peak hours, and an empty server attracts nobody. Start by seeding the server yourself and asking clan members or friends to join during scheduled play sessions. Use SquadJS to display a welcome message and Discord link. Once you reach a core group of 20 to 30 regulars, the server starts filling organically during peak hours.
Apply for the OWI license as soon as your server runs stable for a few days. Being listed in the public browser is the biggest driver of new players. Without it, growth depends entirely on word of mouth and Discord advertising.
Performance optimization
- Set the tick rate to 30 or 40 in
Server.cfg. Higher tick rates improve hit registration but demand more CPU. Most servers use 30. - Restart the server between map changes automatically. Squad servers leak memory over extended sessions.
- Use RCON to monitor player count and switch to smaller layers during off-peak hours.
- Keep the server updated promptly. Squad patches often change netcode, and version mismatches prevent players from connecting.
Do I need the OWI license to run a Squad server?
Not for private use. You only need a license for your server to appear in the public server browser. Private servers for clan practice or events work without one. The license is free but requires an application.
Why is my server tick rate dropping below 20?
CPU saturation during large vehicle fights is the usual cause. Ensure your server has at least 4 dedicated cores with strong single-thread performance. Lowering the tick rate from 40 to 30 can help. Also check that no other processes are competing for CPU time on the same machine.
How many players can I realistically host?
A well-provisioned server handles 100 players at a stable 30 tick rate. With 8 GB of RAM and 4 cores you can run 50 to 80 players comfortably. For the full 100-player experience, go for 16 GB and 6 cores.
Can I run Squad mods on the server?
Yes. Squad supports Steam Workshop mods including custom maps, factions, and total conversions. Add mod IDs to your server configuration. Players download them automatically. Keep in mind that heavily modded servers attract a smaller but more dedicated audience.
Host your Squad server on a HostValues VPS with the CPU and memory to keep 100 soldiers in the fight.
