BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

AKER SOLUTIONS FINANCIAL HOLDING AS

Org. no. 933627209 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 29,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

AKER SOLUTIONS FINANCIAL HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 933627209. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie eller drive industri- og annen tilknyttet virksomhet, forvaltning av kapital og andre funksjoner for konsernet, samt delta i eller overta annen virksomhet.”.

Key figures · 2024

Operating profit
NOK −4,000
Equity
NOK 29,000
Est. value
NOK 28,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AKER SOLUTIONS FINANCIAL HOLDING AS?

AKER SOLUTIONS ASA
AKER SOLUTIONS FINANCIAL HOLDING AS
· NOK −4,000 profit

AKER SOLUTIONS FINANCIAL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AKER SOLUTIONS FINANCIAL HOLDING AS er morselskap for 22 datterselskaper:

Frequently asked questions about AKER SOLUTIONS FINANCIAL HOLDING AS

Who owns AKER SOLUTIONS FINANCIAL HOLDING AS?

AKER SOLUTIONS ASA is the largest registered owner, with 100.0%.

Where is AKER SOLUTIONS FINANCIAL HOLDING AS based?

AKER SOLUTIONS FINANCIAL HOLDING 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.