BIZTRAC BETA
Retail sale of watches and jewellery

FRØKEN HAGEN AS

Org. no. 916476485 Limited company (AS) Nord-Aurdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK −26,000
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−26k kr).

FRØKEN HAGEN AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 916476485. The business is classified under retail sale of watches and jewellery (NACE 47.770). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie og investere i aksjer og eiendom, samt murertjenester, drift av gullsmedbutikk og alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 156,000 in revenue and NOK −26,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK −26,000
Equity
NOK 2.4m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns FRØKEN HAGEN AS?

MARIANNE HÅVELSRUD HAGEN
FRØKEN HAGEN AS
NOK 156,000 rev. · NOK −26,000 profit

FRØKEN HAGEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRØKEN HAGEN AS own?

FRØKEN HAGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRØKEN HAGEN AS

Who owns FRØKEN HAGEN AS?

MARIANNE HÅVELSRUD HAGEN is the largest registered owner, with 100.0%.

What is the revenue of FRØKEN HAGEN AS?

FRØKEN HAGEN AS had revenue of NOK 156,000 in 2024.

Where is FRØKEN HAGEN AS based?

FRØKEN HAGEN AS has its business address in Fagernes.

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.