BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

FRIHEY AS

Org. no. 920610250 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 243,000
Operating profit NOK 200,000
Equity NOK 3.2m
Incorporated 2018
Share capital NOK 30,000

FRIHEY AS is registered as a limited company in Oslo, Oslo with organisation number 920610250. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Medisinsk konsulentvirksomhet og innovasjon, medvirke i andre selskaper innen samme virksomhet, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 243,000 in revenue and NOK 200,000 in operating profit.

Key figures · 2024

Revenue
NOK 243,000
Operating profit
NOK 200,000
Equity
NOK 3.2m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns FRIHEY AS?

FRIDTJOF HEYERDAHL
FRIHEY AS
NOK 243,000 rev. · NOK 200,000 profit

FRIHEY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FRIHEY AS own?

FRIHEY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRIHEY AS

Who owns FRIHEY AS?

FRIDTJOF HEYERDAHL is the largest registered owner, with 100.0%.

What is the revenue of FRIHEY AS?

FRIHEY AS had revenue of NOK 243,000 in 2024.

Who is the general manager of FRIHEY AS?

Fridtjof Heyerdahl is registered as general manager of FRIHEY AS.

Where is FRIHEY AS based?

FRIHEY AS has its business address in Oslo.

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.