BIZTRAC BETA
Retail sale of sports equipment

DYKKERUTSTYR AS

Org. no. 933808629 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 65,000
Operating profit NOK 11,000
Equity NOK 34,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-20 Adresseendring registrert 2026-03-20.

DYKKERUTSTYR AS is registered as a limited company in Larvik, Vestfold with organisation number 933808629. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Import og salg av dykkerutstyr, klær, kurs, service, dykketurer, båtturer, reisebyrå, teinerydding, ryddeaksjoner, vannaktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 65,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 65,000
Operating profit
NOK 11,000
Equity
NOK 34,000
Est. value
NOK 56,000

Financial health · 2024

Liquidity
21.29
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
95.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DYKKERUTSTYR AS?

TRULS SVENDSEN
DYKKERUTSTYR AS
NOK 65,000 rev. · NOK 11,000 profit

DYKKERUTSTYR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYKKERUTSTYR AS

Who owns DYKKERUTSTYR AS?

TRULS SVENDSEN is the largest registered owner, with 50.0%.

What is the revenue of DYKKERUTSTYR AS?

DYKKERUTSTYR AS had revenue of NOK 65,000 in 2024.

Who is the general manager of DYKKERUTSTYR AS?

Magnus Opsahl is registered as general manager of DYKKERUTSTYR AS.

Where is DYKKERUTSTYR AS based?

DYKKERUTSTYR AS has its business address in Stavern.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.