BIZTRAC BETA
Other technical consultancy

HELIX OFFSHORE SERVICES AS

Org. no. 918000615 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 15.7m
Operating profit NOK −9,000
Equity NOK 3.4m
Incorporated 2016
Employees 16
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

HELIX OFFSHORE SERVICES AS is registered as a limited company in Oslo, Oslo with organisation number 918000615. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Yte tekniske og mannskapstjenester til offshore olje- og gassindustrien, og alt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.7m in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.7m
Operating profit
NOK −9,000
Equity
NOK 3.4m
Est. value
NOK 18.2m

Financial health · 2024

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

Who owns HELIX OFFSHORE SERVICES AS?

HELIX OFFSHORE INTERNATIONAL HOLDIN
HELIX OFFSHORE SERVICES AS
NOK 15.7m rev. · NOK −9,000 profit

HELIX OFFSHORE SERVICES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELIX OFFSHORE SERVICES AS

Who owns HELIX OFFSHORE SERVICES AS?

HELIX OFFSHORE INTERNATIONAL HOLDIN is the largest registered owner, with 100.0%.

What is the revenue of HELIX OFFSHORE SERVICES AS?

HELIX OFFSHORE SERVICES AS had revenue of NOK 15.7m in 2024.

Where is HELIX OFFSHORE SERVICES AS based?

HELIX OFFSHORE SERVICES AS has its business address in Oslo.

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.