BIZTRAC BETA
Holiday and other short-stay accommodation

FAGERHAUGEN AS

Org. no. 933883779 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −95,000
Equity NOK −127,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−127k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−95k kr).

FAGERHAUGEN AS is registered as a limited company in Oslo, Oslo with organisation number 933883779. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 4 shares. The company's stated purpose is: “Turisme og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −95,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −95,000
Equity
NOK −127,000

Financial health · 2025

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

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

Who owns FAGERHAUGEN AS?

GJERTRUD WIGGEN KAMSTRUP
FAGERHAUGEN AS
NOK 0 rev. · NOK −95,000 profit

FAGERHAUGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAGERHAUGEN AS

Who owns FAGERHAUGEN AS?

GJERTRUD WIGGEN KAMSTRUP is the largest registered owner, with 50.0%.

What is the revenue of FAGERHAUGEN AS?

FAGERHAUGEN AS had revenue of NOK 0 in 2025.

Who is the general manager of FAGERHAUGEN AS?

Paul Martin Hosen is registered as general manager of FAGERHAUGEN AS.

Where is FAGERHAUGEN AS based?

FAGERHAUGEN 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.