Force Builder
Assemble and compare fleet packages, side by side
Build two force packages, Force A and Force B, from the 760-system database with quantities, and see a transparent, illustrative aggregate of public specs. This is a sum of published numbers, not an operational or targeting assessment.
Illustrative only. Every total is summed directly from the public specifications published on each system page, quantity multiplied by the per-unit figure, with a coverage note wherever data is incomplete. This tool does not model combat outcomes, readiness, logistics or doctrine, and is not an operational or targeting assessment. Always verify against primary sources.
How aggregates are computed
The Force Builder reads the same public specification data published on every WeaponSpecs system page and sums it across the systems and quantities you choose. There is no hidden weighting and no blended score, every number you see is a direct sum, quantity times the per-unit value, of a field that is publicly documented for at least one system in your force.
- 1
Add systems to Force A and Force B
Search either column and add any of the 760 systems in the database, set a quantity for each one.
- 2
Read the transparent totals
Total systems, distinct types, summed cost and every populated capability, each with an honest coverage note.
- 3
Compare Force A vs Force B
A side-by-side breakdown highlights which force is larger on each metric, no blended score, just the sums.
- 4
Share the result
The URL updates as you build, copy it to share the exact two forces with anyone.
What is summed, and its coverage caveats
Unit cost
Publicly documented for roughly 30% of systems. The total always shows a coverage note stating how many systems in the force are priced.
Crew and troop capacity
Crew figures are public for about 62% of systems, troop capacity for a smaller subset, mainly transports and IFVs.
Weapons payload and hardpoints
Documented for roughly 17% of systems, mainly aircraft and strike platforms.
VLS cells and torpedo tubes
Naval-specific fields, documented for a small subset of warships and submarines only.
A capability is hidden entirely when zero systems in your force publish it, so a force never shows a misleading zero for a field nobody in it reports. Absent data is always distinguished from a genuinely-zero sum.
Frequently asked questions
What does the Force Builder actually calculate? +
It sums public specifications across every system you add, weighted by quantity. Total cost, crew, weapons payload, hardpoints, VLS cells, torpedo tubes and cargo payload are all added up (quantity × per-unit value) across the systems in each force. Nothing is averaged and nothing is blended into a single score.
Why do some capability totals not show up? +
A capability is only shown when at least one system in the force publishes that field. Unit cost, for example, is public for roughly 30% of systems in the database, crew figures for about 62%. When zero systems in your force publish a field, it is hidden entirely rather than showing a misleading zero.
What does the cost total actually cover? +
The total cost sums only the systems in your force that have a public unit price. A coverage line always states how many of the systems in the force are priced, so the number is never mistaken for a full-force total when some systems have no public price.
Is this an operational or targeting tool? +
No. The Force Builder is an educational, illustrative aggregator of public specifications. It does not model combat outcomes, logistics, readiness, terrain, doctrine or any operational or targeting factor. It exists to make public spec data easier to total and compare, nothing more.