BIZTRAC BETA
Research and experimental development on natural sciences and engineering

STORMGEO AS

Org. no. 978661017 Limited company (AS) Bergen Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 221.1m
Operating profit NOK 83.0m
Equity NOK 348.6m
Incorporated 1997
Employees 113
Share capital NOK 12.6m

STORMGEO AS is registered as a limited company in Bergen, Vestland with organisation number 978661017. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 1997 and has 113 registered employees. Registered share capital is NOK 12.6m, divided into 125960 shares. The company's stated purpose is: “Eie og drive et værvarslingsselskap samt å engasjere seg i enhver virksomhet som direkte eller indirekte står i forbindelse med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 221.1m in revenue and NOK 83.0m in operating profit.

Key figures · 2024

Revenue
NOK 221.1m
Operating profit
NOK 83.0m
Equity
NOK 348.6m
Est. value
NOK 430.5m

Financial health · 2024

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns STORMGEO AS?

ALFA LAVAL NORDIC AS
STORMGEO AS
NOK 221.1m rev. · NOK 83.0m profit

STORMGEO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORMGEO AS

Who owns STORMGEO AS?

ALFA LAVAL NORDIC AS is the largest registered owner, with 100.0%.

What is the revenue of STORMGEO AS?

STORMGEO AS had revenue of NOK 221.1m in 2024.

Who is the general manager of STORMGEO AS?

Svenn Owe Haugland is registered as general manager of STORMGEO AS.

Where is STORMGEO AS based?

STORMGEO AS has its business address in Bergen.

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.