About the data

Where the Armo wiki statistics come from, how current they are, and what configured, calculated and measured values mean.

Statistics are extracted from a fixed snapshot of the game files. Gameplay explanations are checked separately against the code that handles those actions. Reading a setting alone does not prove how the live game behaves.

How current is it?

Game data was last updated on 17 November 2026.

Configured values

A configured value is read directly from the game, for example the M4's damage. These are shown plainly with no marker.

Calculated values

A value marked calc is derived from configured values with a stated formula. Examples are rate of fire, headshot damage (damage × 2), metres converted from studs, and the damage calculator. Hover or tap the marker to see the formula.

Measured values

Some values only exist while the game runs, such as reload time, which depends on animation length. A measured value is recorded through in-game testing with a method, sample count, tester and date.

No measured values have been recorded yet.

Not documented

Vehicle seats, armour plates, building costs and attachment prices show as Not documented until the team confirms or measures them. Vest protection depends on distance and remaining condition. The guide documents stopped and penetrating outcomes; the calculator lets you select one rather than predicting an individual impact. Earlier fixed hit counts are not protection guarantees.

Units

  • Distances are in Roblox studs. The game uses 0.28 m per stud, and the wiki uses the same for metre conversions.
  • Times are in seconds, money in the game's dollars, and penetration in gameplay millimetres of steel equivalent.
  • Damage is the game's own unit. Injury, blood loss, agony, organ damage and armour can affect the outcome, so a damage number is not a promise of a kill or a fixed time-to-kill.