BIZTRAC BETA
COMPANY REGISTER PROFILE
938151016 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

LYNGDAL DYKKESENTER AS

Org. no. 938151016 Limited company (AS) Lyngdal Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 90,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-06-30.
  • Nylig endring 2026-08-20 Aksjekapital registrert 2026-08-20.

LYNGDAL DYKKESENTER AS is registered as a limited company in Lyngdal, Agder with organisation number 938151016. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2026. Registered share capital is NOK 90,000, divided into 900 shares. The company's stated purpose is: “Drift av dykkesenter, butikk, verksted og servicesenter for dykkerutstyr, fridykkerutstyr, yrkesdykkerutstyr, ROV- og undervannsutstyr, herunder salg, service, vedlikehold, utleie, kurs, opplæring, reiselivsaktiviteter, sjøbaserte opplevelser, formidling, rådgivning og annen naturlig tilknyttet virksomhet.”.

Who owns LYNGDAL DYKKESENTER AS?

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

Frequently asked questions about LYNGDAL DYKKESENTER AS

Where is LYNGDAL DYKKESENTER AS based?

LYNGDAL DYKKESENTER AS has its business address in Lyngdal.

Property

Business address Stamsøyveien 18, 4580 Lyngdal
Cadastral unit 4225-170/106/0/0
Building Butikkbygning · 1 unit

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.