BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

BJØRN HAGEN AS

Org. no. 976030982 Limited company (AS) Alver Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 79.1m
Operating profit NOK 3.5m
Equity NOK 9.6m
Incorporated 1996
Employees 18
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-04-22 Adresseendring registrert 2026-04-22.

BJØRN HAGEN AS is registered as a limited company in Alver, Vestland with organisation number 976030982. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1996 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handelsvirksomhet, eie eierandeler i annen virksomhet og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 79.1m in revenue and NOK 3.5m in operating profit.

Key figures · 2024

Revenue
NOK 79.1m
Operating profit
NOK 3.5m
Equity
NOK 9.6m
Est. value
NOK 18.6m

Financial health · 2024

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.5%
Very good
Equity as a share of total capital

Who owns BJØRN HAGEN AS?

PANTHEON HOLDING AS
BJØRN HAGEN AS
NOK 79.1m rev. · NOK 3.5m profit

BJØRN HAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRN HAGEN AS

Who owns BJØRN HAGEN AS?

PANTHEON HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BJØRN HAGEN AS?

BJØRN HAGEN AS had revenue of NOK 79.1m in 2024.

Who is the general manager of BJØRN HAGEN AS?

Gisle Skauge is registered as general manager of BJØRN HAGEN AS.

Where is BJØRN HAGEN AS based?

BJØRN HAGEN AS has its business address in Frekhaug.

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.