BIZTRAC BETA
Development of building projects

HOVLANDBANEN UTVIKLING AS

Org. no. 933155374 Limited company (AS) Surnadal Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 47,000
Operating profit NOK −903,000
Equity NOK −8.5m
Incorporated 2024
Share capital NOK 7.5m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−8,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−903k kr).

HOVLANDBANEN UTVIKLING AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 933155374. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 7.5m, divided into 3000 shares. The company's stated purpose is: “Å eie, erverve, utvikle og selge eiendom/utbyggingsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 47,000 in revenue and NOK −903,000 in operating profit.

Key figures · 2024

Revenue
NOK 47,000
Operating profit
NOK −903,000
Equity
NOK −8.5m

Financial health · 2024

Liquidity
18.59
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-10.5%
Weak
Equity as a share of total capital

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

Who owns HOVLANDBANEN UTVIKLING AS?

AURORA EIENDOM AS
HOVLANDBANEN UTVIKLING AS
NOK 47,000 rev. · NOK −903,000 profit

HOVLANDBANEN UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOVLANDBANEN UTVIKLING AS

Who owns HOVLANDBANEN UTVIKLING AS?

AURORA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of HOVLANDBANEN UTVIKLING AS?

HOVLANDBANEN UTVIKLING AS had revenue of NOK 47,000 in 2024.

Where is HOVLANDBANEN UTVIKLING AS based?

HOVLANDBANEN UTVIKLING AS has its business address in Surnadal.

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.