BIZTRAC BETA
COMPANY REGISTER PROFILE
936722970 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Restaurant activities

NANSEN CAFE AS

Org. no. 936722970 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Employees 17
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-14.

NANSEN CAFE AS is registered as a limited company in Bærum, Akershus with organisation number 936722970. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restaurant/kafe, inkludert, men ikke begrenset til, produksjon og salg av mat- og drikkevarer for konsum på stedet, take-away og catering. Herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”.

Who owns NANSEN CAFE AS?

NANSEN CAFE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NANSEN CAFE AS

Who owns NANSEN CAFE AS?

MARTE RØNNING MYRVOLD is the largest registered owner, with 100.0%.

Who is the general manager of NANSEN CAFE AS?

Marte Rønning Myrvold is registered as general manager of NANSEN CAFE AS.

Where is NANSEN CAFE AS based?

NANSEN CAFE AS has its business address in Snarøya.

Property

Business address Langoddveien 87B, 1367 Snarøya
Cadastral unit 3201-41/436/0/0
Building Tomannsbolig, vertikal · 1 unit

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