BIZTRAC BETA
Transport via pipeline

CAPEOMEGA GAS TRANSPORTATION AS

Org. no. 925125814 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 392.8m
Operating profit NOK 375.2m
Equity NOK 4.4bn
Incorporated 2020
Share capital NOK 6.9m

Signals

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

CAPEOMEGA GAS TRANSPORTATION AS is registered as a limited company in Bærum, Akershus with organisation number 925125814. The business is classified under transport via pipeline (NACE 49.500). The company was incorporated in 2020. Registered share capital is NOK 6.9m, divided into 6260000 shares. The company's stated purpose is: “Eie og forvalte aksjer i andre selskaper innenfor gasstransportbransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 392.8m in revenue and NOK 375.2m in operating profit.

Key figures · 2024

Revenue
NOK 392.8m
Operating profit
NOK 375.2m
Equity
NOK 4.4bn
Est. value
NOK 3.4bn

Financial health · 2024

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

Who owns CAPEOMEGA GAS TRANSPORTATION AS?

BUOY JV BIDCO AS
CAPEOMEGA GAS TRANSPORTATION AS
NOK 392.8m rev. · NOK 375.2m profit

CAPEOMEGA GAS TRANSPORTATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAPEOMEGA GAS TRANSPORTATION AS

Who owns CAPEOMEGA GAS TRANSPORTATION AS?

BUOY JV BIDCO AS is the largest registered owner, with 100.0%.

What is the revenue of CAPEOMEGA GAS TRANSPORTATION AS?

CAPEOMEGA GAS TRANSPORTATION AS had revenue of NOK 392.8m in 2024.

Where is CAPEOMEGA GAS TRANSPORTATION AS based?

CAPEOMEGA GAS TRANSPORTATION AS has its business address in Lysaker.

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.