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

OLAV N. LOHNE HOLDING AS

Org. no. 936679730 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

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

OLAV N. LOHNE HOLDING AS is registered as a limited company in Tromsø, Troms with organisation number 936679730. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i datterselskap.”.

Who owns OLAV N. LOHNE HOLDING AS?

OLAV N. LOHNE HOLDING AS

OLAV N. LOHNE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLAV N. LOHNE HOLDING AS own?

OLAV N. LOHNE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLAV N. LOHNE HOLDING AS

Who owns OLAV N. LOHNE HOLDING AS?

OLAV NILSEN LOHNE is the largest registered owner, with 100.0%.

Who is the general manager of OLAV N. LOHNE HOLDING AS?

Olav Nilsen Lohne is registered as general manager of OLAV N. LOHNE HOLDING AS.

Where is OLAV N. LOHNE HOLDING AS based?

OLAV N. LOHNE HOLDING AS has its business address in Tromsø.

Property

Business address Balsfjordvinden 66, 9006 Tromsø
Cadastral unit 5501-119/3867/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 17 units

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