BIZTRAC BETA
Supply and other sea transport offshore services

KRISTIANSUND TAUBÅTSERVICE AS

Org. no. 927573318 Limited company (AS) Kristiansund Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 37.5m
Operating profit NOK 7.5m
Equity NOK 41.6m
Incorporated 2021
Employees 19
Share capital NOK 100,000

KRISTIANSUND TAUBÅTSERVICE AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 927573318. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2021 and has 19 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive rederivirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 37.5m in revenue and NOK 7.5m in operating profit.

Key figures · 2025

Revenue
NOK 37.5m
Operating profit
NOK 7.5m
Equity
NOK 41.6m
Est. value
NOK 45.1m

Financial health · 2025

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

Who owns KRISTIANSUND TAUBÅTSERVICE AS?

TAUBÅTSERVICE HOLDING AS
KRISTIANSUND TAUBÅTSERVICE AS
NOK 37.5m rev. · NOK 7.5m profit

KRISTIANSUND TAUBÅTSERVICE AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRISTIANSUND TAUBÅTSERVICE AS

Who owns KRISTIANSUND TAUBÅTSERVICE AS?

TAUBÅTSERVICE HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of KRISTIANSUND TAUBÅTSERVICE AS?

KRISTIANSUND TAUBÅTSERVICE AS had revenue of NOK 37.5m in 2025.

Where is KRISTIANSUND TAUBÅTSERVICE AS based?

KRISTIANSUND TAUBÅTSERVICE AS has its business address in Frei.

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.