BIZTRAC BETA
Supply and other sea transport offshore services

OLSEN SJØSERVICE AS

Org. no. 928635090 Limited company (AS) Ørland Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 446,000
Equity NOK 240,000
Incorporated 2022
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-05-06 Adresseendring registrert 2026-05-06.

OLSEN SJØSERVICE AS is registered as a limited company in Ørland, Trøndelag with organisation number 928635090. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Servicetjenester, salg av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 446,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 446,000
Equity
NOK 240,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns OLSEN SJØSERVICE AS?

O. HOLDING AS
OLSEN SJØSERVICE AS
NOK 3.9m rev. · NOK 446,000 profit

OLSEN SJØSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLSEN SJØSERVICE AS

Who owns OLSEN SJØSERVICE AS?

O. HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OLSEN SJØSERVICE AS?

OLSEN SJØSERVICE AS had revenue of NOK 3.9m in 2025.

Who is the general manager of OLSEN SJØSERVICE AS?

Kenneth Olsen is registered as general manager of OLSEN SJØSERVICE AS.

Where is OLSEN SJØSERVICE AS based?

OLSEN SJØSERVICE AS has its business address in Vallersund.

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.