BIZTRAC BETA
Rental and operating of own or leased real estate

HARESTIGEN 5 AS

Org. no. 925207772 Limited company (AS) Vestby Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 18,000
Operating profit NOK −53,000
Equity NOK 4,000
Incorporated 2020
Share capital NOK 40,000

Signals

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

HARESTIGEN 5 AS is registered as a limited company in Vestby, Akershus with organisation number 925207772. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “Kjøp, forvaltning og utleie av hytte i Harestigen 5 i Uvdal Skisenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
Operating profit
NOK −53,000
Equity
NOK 4,000
Est. value
NOK 4,000

Financial health · 2024

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

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

Who owns HARESTIGEN 5 AS?

TLW AS
HARESTIGEN 5 AS
NOK 18,000 rev. · NOK −53,000 profit

HARESTIGEN 5 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HARESTIGEN 5 AS

Who owns HARESTIGEN 5 AS?

TLW AS is the largest registered owner, with 62.0%.

What is the revenue of HARESTIGEN 5 AS?

HARESTIGEN 5 AS had revenue of NOK 18,000 in 2025.

Where is HARESTIGEN 5 AS based?

HARESTIGEN 5 AS has its business address in Son.

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.