biztrac. BETA
COMPANY REGISTER PROFILE
996496147 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of industrial gases

AIR LIQUIDE OFFSHORE AS

Org. no. 996496147 Limited company (AS) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 57.4m
Operating profit NOK 5.1m
Equity NOK 27.8m
Incorporated 2010
Employees 9
Share capital NOK 4.0m

AIR LIQUIDE OFFSHORE AS is registered as a limited company in Bergen, Vestland with organisation number 996496147. The business is classified under manufacture of industrial gases (NACE 20.110). The company was incorporated in 2010 and has 9 registered employees. Registered share capital is NOK 4.0m, divided into 4000 shares. The company's stated purpose is: “Levering av industriell og medisinsk gass til offshore industrien.”. The most recent filed accounts, for the 2025 financial year, show NOK 57.4m in revenue and NOK 5.1m in operating profit.

Key figures · 2025

Revenue
NOK 57.4m
▲ +16 %
Operating profit
NOK 5.1m
▼ −22 %
Equity
NOK 27.8m
▼ −4 %
Est. value
NOK 39.5m

Financial health · 2025

Liquidity
4.22
Very good
Current assets ÷ current liabilities
Profitability
14.3%
Good
Return on total assets
Solidity
79.4%
Very good
Equity as a share of total capital

Who owns AIR LIQUIDE OFFSHORE AS?

AIR LIQUIDE OIL & GAS SERVICES LTD GB
AIR LIQUIDE OFFSHORE AS
NOK 57.4m rev. · NOK 5.1m profit

AIR LIQUIDE OFFSHORE AS has 1 registered shareholder:

  • AIR LIQUIDE OIL & GAS SERVICES LTD 100.0%
All shareholders and roles →

Frequently asked questions about AIR LIQUIDE OFFSHORE AS

Who owns AIR LIQUIDE OFFSHORE AS?

AIR LIQUIDE OIL & GAS SERVICES LTD is the largest registered owner, with 100.0%.

What is the revenue of AIR LIQUIDE OFFSHORE AS?

AIR LIQUIDE OFFSHORE AS had revenue of NOK 57.4m in 2025.

Where is AIR LIQUIDE OFFSHORE AS based?

AIR LIQUIDE OFFSHORE AS has its business address in Kokstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.