BIZTRAC BETA
Uoppgitt

FREHEN HOLDING AS

Org. no. 929919742 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 8,000
Incorporated 2022
Share capital NOK 30,000

FREHEN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 929919742. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i verdipapir, eigedom og anna forretningsverksemd. Selskapet kan også engasjere seg i andre foretak uansett formål og selskapsform.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 8,000
Est. value
NOK 9,000

Financial health · 2024

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

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

Who owns FREHEN HOLDING AS?

HÅVARD ANGELL AUGDAL
FREHEN HOLDING AS
NOK 0 rev. · NOK 0 profit

FREHEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FREHEN HOLDING AS own?

FREHEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FREHEN HOLDING AS

Who owns FREHEN HOLDING AS?

HÅVARD ANGELL AUGDAL is the largest registered owner, with 100.0%.

What is the revenue of FREHEN HOLDING AS?

FREHEN HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of FREHEN HOLDING AS?

Håvard Angell Augdal is registered as general manager of FREHEN HOLDING AS.

Where is FREHEN HOLDING AS based?

FREHEN HOLDING AS has its business address in Bønes.

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.