BIZTRAC BETA
COMPANY REGISTER PROFILE
856736202 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING

Org. no. 856736202 Association/club/organisation (FLI) Oslo Active
Ownership graph ↗

MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING is registered as a association/club/organisation in Oslo, Oslo with organisation number 856736202. The business is classified under other activities of other membership organisations (NACE 94.992). The company's stated purpose is: “Å arbeide for fremme av allmenne og forretnings- messige interesser i strøket, virke for et godt og varig forhold mellom medlemmene, samt være kontaktledd overfor offentlig myndigheter o.l. Foreningen kan søke samarbeide med andre foren- inger med samme eller lignende formål.”.

Who owns MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING?

No shareholders are registered for MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING

Who is the general manager of MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING?

Jon Annar Berntsen is registered as general manager of MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING.

Where is MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING based?

MAJORSTUEN OG BOGSTADVEIEN NÆRINGSFORENING has its business address in Oslo.

Property

Business address Hegdehaugsveien 34, 0352 Oslo
Cadastral unit 301-214/100/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 42 units

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