BIZTRAC BETA
Other technical consultancy

UNDERVANNSTEKNIKK.NO AS

Org. no. 928870545 Limited company (AS) Indre Østfold Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 13,000
Incorporated 2022
Share capital NOK 30,000

UNDERVANNSTEKNIKK.NO AS is registered as a limited company in Indre Østfold, Østfold with organisation number 928870545. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Fjernstyrte tjenester/funksjoner under vann ved bruk av undervanns-robot/ROV (remotely operated vehickle).”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 13,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns UNDERVANNSTEKNIKK.NO AS?

JON ANDERS HESLESKAUG
UNDERVANNSTEKNIKK.NO AS
NOK 0 rev. · NOK 0 profit

UNDERVANNSTEKNIKK.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UNDERVANNSTEKNIKK.NO AS

Who owns UNDERVANNSTEKNIKK.NO AS?

JON ANDERS HESLESKAUG is the largest registered owner, with 100.0%.

What is the revenue of UNDERVANNSTEKNIKK.NO AS?

UNDERVANNSTEKNIKK.NO AS had revenue of NOK 0 in 2025.

Who is the general manager of UNDERVANNSTEKNIKK.NO AS?

Jon Anders Hesleskaug is registered as general manager of UNDERVANNSTEKNIKK.NO AS.

Where is UNDERVANNSTEKNIKK.NO AS based?

UNDERVANNSTEKNIKK.NO AS has its business address in Spydeberg.

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.