BIZTRAC BETA
Rental and operating of own or leased real estate

STRANDPARKEN EIENDOM AS

Org. no. 985825173 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 16.9m
Operating profit NOK 8.7m
Equity NOK 110.9m
Incorporated 2003
Share capital NOK 529,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STRANDPARKEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 985825173. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 529,000, divided into 528642 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.9m in revenue and NOK 8.7m in operating profit.

Key figures · 2024

Revenue
NOK 16.9m
Operating profit
NOK 8.7m
Equity
NOK 110.9m
Est. value
NOK 103.3m

Financial health · 2024

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

Who owns STRANDPARKEN EIENDOM AS?

ASSET BUYOUT PARTNERS AS
STRANDPARKEN EIENDOM AS
NOK 16.9m rev. · NOK 8.7m profit

STRANDPARKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRANDPARKEN EIENDOM AS

Who owns STRANDPARKEN EIENDOM AS?

ASSET BUYOUT PARTNERS AS is the largest registered owner, with 100.0%.

What is the revenue of STRANDPARKEN EIENDOM AS?

STRANDPARKEN EIENDOM AS had revenue of NOK 16.9m in 2024.

Where is STRANDPARKEN EIENDOM AS based?

STRANDPARKEN EIENDOM 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.