biztrac. BETA
COMPANY REGISTER PROFILE
934411447 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of fertilisers and nitrogen compounds

EYDEHAVN GREEN AMMONIA AS

Org. no. 934411447 Limited company (AS) Arendal Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −15.6m
Equity NOK −15.5m
Incorporated 2024
Share capital NOK 117,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15,5 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15,6 mill kr).

EYDEHAVN GREEN AMMONIA AS is registered as a limited company in Arendal, Agder with organisation number 934411447. The business is classified under manufacture of fertilisers and nitrogen compounds (NACE 20.150). The company was incorporated in 2024. Registered share capital is NOK 117,000, divided into 15648 shares. The company's stated purpose is: “Produksjon, distribusjon og salg av grønn hydrogen og grønn ammoniakk.”.

Key figures · 2025

Operating profit
NOK −15.6m
▼ −103359 %
Equity
NOK −15.5m
▼ −1152 %

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
-85.9%
Not satisfactory
Return on total assets
Solidity
-79.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EYDEHAVN GREEN AMMONIA AS?

EYDEHAVN GREEN AMMONIA AS
· NOK −15.6m profit

EYDEHAVN GREEN AMMONIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EYDEHAVN GREEN AMMONIA AS

Who owns EYDEHAVN GREEN AMMONIA AS?

NORTH AMMONIA AS is the largest registered owner, with 100.0%.

Who is the general manager of EYDEHAVN GREEN AMMONIA AS?

Mikkel Tørud is registered as general manager of EYDEHAVN GREEN AMMONIA AS.

Where is EYDEHAVN GREEN AMMONIA AS based?

EYDEHAVN GREEN AMMONIA AS has its business address in Eydehavn.

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

Report a problem

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