BIZTRAC BETA
COMPANY REGISTER PROFILE
837014522 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Joinery installation

KONGSGÅRD DRIFT OG MONTASJE AS

Org. no. 837014522 Limited company (AS) Larvik Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 300,000

Signals

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

KONGSGÅRD DRIFT OG MONTASJE AS is registered as a limited company in Larvik, Vestfold with organisation number 837014522. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2026. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Utføring av snekkerarbeid, vaktmestertjenester samt alt som naturlig står i forbindelse med dette, herunder investeringer og deltagelse i andre selskaper.”.

Who owns KONGSGÅRD DRIFT OG MONTASJE AS?

No shareholders are registered for KONGSGÅRD DRIFT OG MONTASJE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about KONGSGÅRD DRIFT OG MONTASJE AS

Who is the general manager of KONGSGÅRD DRIFT OG MONTASJE AS?

Bjørn Thonhaugen Kongsgård is registered as general manager of KONGSGÅRD DRIFT OG MONTASJE AS.

Where is KONGSGÅRD DRIFT OG MONTASJE AS based?

KONGSGÅRD DRIFT OG MONTASJE AS has its business address in Larvik.

Property

Business address Dronning Gydas vei 11, 3269 Larvik
Cadastral unit 3909-2010/51/0/0
Building Tomannsbolig, horisontaldelt · 2 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.