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

LAGERSJEFEN CONTAINER AS

Org. no. 937255527 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-02-02.
  • Nylig endring 2026-07-23 Adresseendring registrert 2026-07-23.

LAGERSJEFEN CONTAINER AS is registered as a limited company in Oslo, Oslo with organisation number 937255527. 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 300 shares. The company's stated purpose is: “Utleie av minilager, lagercontainere, og fast eiendom.”.

Former names: BRA MINILAGER AS

Who owns LAGERSJEFEN CONTAINER AS?

No shareholders are registered for LAGERSJEFEN CONTAINER AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Group structure

LAGERSJEFEN CONTAINER AS er morselskap for 1 datterselskap:

Frequently asked questions about LAGERSJEFEN CONTAINER AS

Who is the general manager of LAGERSJEFEN CONTAINER AS?

Øystein Grøstad is registered as general manager of LAGERSJEFEN CONTAINER AS.

Where is LAGERSJEFEN CONTAINER AS based?

LAGERSJEFEN CONTAINER AS has its business address in Oslo.

Property

Business address Haakon VIIs gate 5, 0161 Oslo
Cadastral unit 301-209/130/0/0

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