BIZTRAC BETA
COMPANY REGISTER PROFILE
988827355 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

FAGERHØI AS

Org. no. 988827355 Limited company (AS) Sør-Fron Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −75,000
Equity NOK 38.4m
Incorporated 2005
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−75k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FAGERHØI AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 988827355. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Investering i omløps- og anleggsmidler, samt engasjement i underliggende og andre selskapers drift.”.

Key figures · 2025

Operating profit
NOK −75,000
▼ −58 %
Equity
NOK 38.4m
▲ +3 %
Est. value
NOK 30.7m

Financial health · 2025

Liquidity
25.38
Very good
Current assets ÷ current liabilities
Profitability
3.9%
Weak
Return on total assets
Solidity
97.6%
Very good
Equity as a share of total capital

Who owns FAGERHØI AS?

FAGERHØI AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FAGERHØI AS own?

FAGERHØI AS holds a stake in 1 company:

See the full ownership structure →

Group structure

FAGERHØI AS er morselskap for 1 datterselskap:

Frequently asked questions about FAGERHØI AS

Who owns FAGERHØI AS?

CHRISTIAN ALGODT HOVIND is the largest registered owner, with 51.0%.

Who is the general manager of FAGERHØI AS?

Christian Algodt Hovind is registered as general manager of FAGERHØI AS.

Where is FAGERHØI AS based?

FAGERHØI AS has its business address in Sør-Fron.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.