BIZTRAC BETA
Development of building projects

HOVLANDSFJELL AS

Org. no. 992221828 Limited company (AS) Modum Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 9,000
Equity NOK −83,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−83k kr).

HOVLANDSFJELL AS is registered as a limited company in Modum, Buskerud with organisation number 992221828. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendommer, drift av eiendommer, eie aksjer/andeler i andre selskap samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 9,000
Equity
NOK −83,000
Est. value
NOK 94,000

Financial health · 2024

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

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

Who owns HOVLANDSFJELL AS?

KJELL FINSRUD AS
HOVLANDSFJELL AS
NOK 0 rev. · NOK 9,000 profit

HOVLANDSFJELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVLANDSFJELL AS

Who owns HOVLANDSFJELL AS?

KJELL FINSRUD AS is the largest registered owner, with 100.0%.

What is the revenue of HOVLANDSFJELL AS?

HOVLANDSFJELL AS had revenue of NOK 0 in 2024.

Who is the general manager of HOVLANDSFJELL AS?

Kjell Vidar Finsrud is registered as general manager of HOVLANDSFJELL AS.

Where is HOVLANDSFJELL AS based?

HOVLANDSFJELL AS has its business address in Vikersund.

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.