BIZTRAC BETA
Rental and operating of own or leased real estate

STORHAUGVEIEN AS

Org. no. 929978110 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 280,000
Operating profit NOK −281
Equity NOK 45,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−281 kr).

STORHAUGVEIEN AS is registered as a limited company in Stavanger, Rogaland with organisation number 929978110. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Boligutleie, samt hva som knyttes til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 280,000 in revenue and NOK −281 in operating profit.

Key figures · 2025

Revenue
NOK 280,000
Operating profit
NOK −281
Equity
NOK 45,000
Est. value
NOK 41,000

Financial health · 2025

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

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

Who owns STORHAUGVEIEN AS?

OLAV ROLFSEN BOLIGUTLEIE AS
STORHAUGVEIEN AS
NOK 280,000 rev. · NOK −281 profit

STORHAUGVEIEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORHAUGVEIEN AS

Who owns STORHAUGVEIEN AS?

OLAV ROLFSEN BOLIGUTLEIE AS is the largest registered owner, with 100.0%.

What is the revenue of STORHAUGVEIEN AS?

STORHAUGVEIEN AS had revenue of NOK 280,000 in 2025.

Who is the general manager of STORHAUGVEIEN AS?

Harald Rolfsen is registered as general manager of STORHAUGVEIEN AS.

Where is STORHAUGVEIEN AS based?

STORHAUGVEIEN AS has its business address in Hafrsfjord.

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.