BIZTRAC BETA
Construction of water projects

BONDHUS SJØTJENESTER AS

Org. no. 931114816 Limited company (AS) Tysnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 49,000
Operating profit NOK 23,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

BONDHUS SJØTJENESTER AS is registered as a limited company in Tysnes, Vestland with organisation number 931114816. The business is classified under construction of water projects (NACE 42.910). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levere tjenester i form av kranoperasjoner, sleping, frakt, undervannsoperasjoner og det som naturlig tilhører med arbeidsbåt.”. The most recent filed accounts, for the 2024 financial year, show NOK 49,000 in revenue and NOK 23,000 in operating profit.

Key figures · 2024

Revenue
NOK 49,000
Operating profit
NOK 23,000
Equity
NOK 29,000
Est. value
NOK 79,000

Financial health · 2024

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.7%
Weak
Equity as a share of total capital

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

Who owns BONDHUS SJØTJENESTER AS?

MORTEN BONDHUS
BONDHUS SJØTJENESTER AS
NOK 49,000 rev. · NOK 23,000 profit

BONDHUS SJØTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BONDHUS SJØTJENESTER AS

Who owns BONDHUS SJØTJENESTER AS?

MORTEN BONDHUS is the largest registered owner, with 100.0%.

What is the revenue of BONDHUS SJØTJENESTER AS?

BONDHUS SJØTJENESTER AS had revenue of NOK 49,000 in 2024.

Who is the general manager of BONDHUS SJØTJENESTER AS?

Morten Bondhus is registered as general manager of BONDHUS SJØTJENESTER AS.

Where is BONDHUS SJØTJENESTER AS based?

BONDHUS SJØTJENESTER AS has its business address in Uggdal.

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.