BIZTRAC BETA
COMPANY REGISTER PROFILE
937492863 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

MARRYLOU ENTERPRISES AS

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

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-03-24.

MARRYLOU ENTERPRISES AS is registered as a limited company in Oslo, Oslo with organisation number 937492863. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og andre finansielle eiendeler, eierskap og forvaltning av andre selskaper, samt å yte administrative og rådgivende tjenester. Selskapet kan også drive annen virksomhet som står i naturlig forbindelse med dette.”.

Who owns MARRYLOU ENTERPRISES AS?

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

Frequently asked questions about MARRYLOU ENTERPRISES AS

Who is the general manager of MARRYLOU ENTERPRISES AS?

Marianne Hauknes is registered as general manager of MARRYLOU ENTERPRISES AS.

Where is MARRYLOU ENTERPRISES AS based?

MARRYLOU ENTERPRISES AS has its business address in Oslo.

Property

Business address Gustav Vigelands vei 54, 0274 Oslo
Cadastral unit 301-3/496/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 20 units

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