BIZTRAC BETA
Other specialised construction activities n.e.c.

DYKK OG BETONG AS

Org. no. 919211024 Limited company (AS) Kragerø Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK −216,000
Equity NOK 1.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−216k kr).

DYKK OG BETONG AS is registered as a limited company in Kragerø, Telemark with organisation number 919211024. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Dykketjenester herunder reparasjon av konstruksjoner under vann, samt alt innen betongarbeid, og annen tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK −216,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK −216,000
Equity
NOK 1.7m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.0%
Very good
Equity as a share of total capital

Who owns DYKK OG BETONG AS?

ARILD BENTSEN
DYKK OG BETONG AS
NOK 2.6m rev. · NOK −216,000 profit

DYKK OG BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYKK OG BETONG AS

Who owns DYKK OG BETONG AS?

ARILD BENTSEN is the largest registered owner, with 100.0%.

What is the revenue of DYKK OG BETONG AS?

DYKK OG BETONG AS had revenue of NOK 2.6m in 2025.

Who is the general manager of DYKK OG BETONG AS?

Arild Bentsen is registered as general manager of DYKK OG BETONG AS.

Where is DYKK OG BETONG AS based?

DYKK OG BETONG AS has its business address in Kragerø.

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.