BIZTRAC BETA
Uoppgitt

FRIHEIM HOLDING AS

Org. no. 935606896 Limited company (AS) Flakstad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

FRIHEIM HOLDING AS is registered as a limited company in Flakstad, Nordland with organisation number 935606896. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 28 shares. The company's stated purpose is: “Investering i og forvaltning av aksjer og andre verdipapirer, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 18,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns FRIHEIM HOLDING AS?

ALEXANDER KRISTIANSEN
FRIHEIM HOLDING AS
NOK 0 rev. · NOK −5,000 profit

FRIHEIM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRIHEIM HOLDING AS

Who owns FRIHEIM HOLDING AS?

ALEXANDER KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of FRIHEIM HOLDING AS?

FRIHEIM HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of FRIHEIM HOLDING AS?

Alexander Kristiansen is registered as general manager of FRIHEIM HOLDING AS.

Where is FRIHEIM HOLDING AS based?

FRIHEIM HOLDING AS has its business address in Napp.

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.