BIZTRAC BETA
Supply and other sea transport offshore services

SEA1 AHTS POOL AS

Org. no. 895871362 Limited company (AS) Kristiansand Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 61.2m
Operating profit NOK 153.4m
Equity NOK 114.8m
Incorporated 2010
Share capital NOK 1.3m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SEA1 AHTS POOL AS is registered as a limited company in Kristiansand, Agder with organisation number 895871362. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2010. Registered share capital is NOK 1.3m, divided into 13000 shares. The company's stated purpose is: “Poolsamarbeid, herunder drift av offshorefartøyer, shippingvirksomhet, entreprenørvirksomhet, samt hva som står i forbindelse med de nevnte aktivitetsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.2m in revenue and NOK 153.4m in operating profit.

Key figures · 2024

Revenue
NOK 61.2m
Operating profit
NOK 153.4m
Equity
NOK 114.8m
Est. value
NOK 523.3m

Financial health · 2024

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

Who owns SEA1 AHTS POOL AS?

SEA1 OFFSHORE INC.
SEA1 AHTS POOL AS
NOK 61.2m rev. · NOK 153.4m profit

SEA1 AHTS POOL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEA1 AHTS POOL AS

Who owns SEA1 AHTS POOL AS?

SEA1 OFFSHORE INC. is the largest registered owner, with 100.0%.

What is the revenue of SEA1 AHTS POOL AS?

SEA1 AHTS POOL AS had revenue of NOK 61.2m in 2024.

Where is SEA1 AHTS POOL AS based?

SEA1 AHTS POOL AS has its business address in Kristiansand S.

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.