BIZTRAC BETA
COMPANY REGISTER PROFILE
990637156 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

MARIDALSVEIEN 323 AS

Org. no. 990637156 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Incorporated 2006
Share capital NOK 374,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-07 Adresseendring registrert 2026-07-07.

MARIDALSVEIEN 323 AS is registered as a limited company in Oslo, Oslo with organisation number 990637156. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 374,000, divided into 373814 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i og utvikle fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Former names: MARIDALSVEIEN 323 EIENDOM AS

Who owns MARIDALSVEIEN 323 AS?

MARIDALSVEIEN 323 AS

MARIDALSVEIEN 323 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARIDALSVEIEN 323 AS

Who owns MARIDALSVEIEN 323 AS?

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

Where is MARIDALSVEIEN 323 AS based?

MARIDALSVEIEN 323 AS has its business address in Oslo.

Property

Business address Silurveien 2, 0380 Oslo
Cadastral unit 301-28/1139/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

167 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.