BIZTRAC BETA
Rental and operating of own or leased real estate

PARKERINGSHUSET SARPSBORG AS

Org. no. 992017295 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 621,000
Operating profit NOK −911,000
Equity NOK 21.0m
Incorporated 2007
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−911k kr).

PARKERINGSHUSET SARPSBORG AS is registered as a limited company in Oslo, Oslo with organisation number 992017295. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.2m, divided into 10000 shares. The company's stated purpose is: “Kjøp, salg, utleie, drift og utvikling av fast eiendom, og hva som hermed står i forbindelse, samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 621,000 in revenue and NOK −911,000 in operating profit.

Key figures · 2024

Revenue
NOK 621,000
Operating profit
NOK −911,000
Equity
NOK 21.0m
Est. value
NOK 15.1m

Financial health · 2024

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
94.8%
Very good
Equity as a share of total capital

Who owns PARKERINGSHUSET SARPSBORG AS?

ESTATEC AS
PARKERINGSHUSET SARPSBORG AS
NOK 621,000 rev. · NOK −911,000 profit

PARKERINGSHUSET SARPSBORG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARKERINGSHUSET SARPSBORG AS

Who owns PARKERINGSHUSET SARPSBORG AS?

ESTATEC AS is the largest registered owner, with 100.0%.

What is the revenue of PARKERINGSHUSET SARPSBORG AS?

PARKERINGSHUSET SARPSBORG AS had revenue of NOK 621,000 in 2024.

Where is PARKERINGSHUSET SARPSBORG AS based?

PARKERINGSHUSET SARPSBORG AS has its business address in Oslo.

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.