BIZTRAC BETA
COMPANY REGISTER PROFILE
937476477 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

OLE DEVIKS VEI 40 AS

Org. no. 937476477 Limited company (AS) Oslo Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-03-17.
  • Nylig endring 2026-07-01 Adresseendring registrert 2026-07-01.

OLE DEVIKS VEI 40 AS is registered as a limited company in Oslo, Oslo with organisation number 937476477. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, eie og leie ut fast eiendom; samt alt hva herved står i forbindelse.”.

Former names: NFH 2603117 AS

Who owns OLE DEVIKS VEI 40 AS?

No shareholders are registered for OLE DEVIKS VEI 40 AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about OLE DEVIKS VEI 40 AS

Who is the general manager of OLE DEVIKS VEI 40 AS?

Børre Vegard Skjolden is registered as general manager of OLE DEVIKS VEI 40 AS.

Where is OLE DEVIKS VEI 40 AS based?

OLE DEVIKS VEI 40 AS has its business address in Oslo.

Property

Business address c/o Eiendomsspar AS Fridtjof Nansens plass 4, 0160 Oslo
Cadastral unit 301-209/144/0/0

357 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.