BIZTRAC BETA
Manufacture of weapons and ammunition

GREEN AMMO AS

Org. no. 922320837 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK −2.8m
Equity NOK 74.6m
Incorporated 2019
Employees 8
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,8 mill kr).

GREEN AMMO AS is registered as a limited company in Skien, Telemark with organisation number 922320837. The business is classified under manufacture of weapons and ammunition (NACE 25.300). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 1.2m, divided into 49900 shares. The company's stated purpose is: “Utvikling, produksjon og salg av simulert ammunisjon, eierskap i andre selskaper med tilsvarende virksomhet, samt all virksomhet knyttet til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK −2.8m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK −2.8m
Equity
NOK 74.6m
Est. value
NOK 44.6m

Financial health · 2024

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.7%
Very good
Equity as a share of total capital

Who owns GREEN AMMO AS?

OLE ANDREAS HALVORSEN
GREEN AMMO AS
NOK 10.1m rev. · NOK −2.8m profit

GREEN AMMO AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about GREEN AMMO AS

Who owns GREEN AMMO AS?

OLE ANDREAS HALVORSEN is the largest registered owner, with 96.0%.

What is the revenue of GREEN AMMO AS?

GREEN AMMO AS had revenue of NOK 10.1m in 2024.

Who is the general manager of GREEN AMMO AS?

Rolf Inge Roth is registered as general manager of GREEN AMMO AS.

Where is GREEN AMMO AS based?

GREEN AMMO AS has its business address in Skien.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.