biztrac. BETA
COMPANY REGISTER PROFILE
833589792 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

FARADAY TOPCO AS

Org. no. 833589792 Limited company (AS) Oslo Incorporated 2024 Active
Operating profit NOK −2.0m
Equity NOK 6.5bn
Incorporated 2024
Share capital NOK 65.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

FARADAY TOPCO AS is registered as a limited company in Oslo, Oslo with organisation number 833589792. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 65.0m, divided into 6498099792 shares. The company's stated purpose is: “Å være en ledende leverandør av teknologi og bidra til å muliggjøre den grønne omstillingen ved å utvikle og tilby i ulike teknologiske tjenester innen energi, kraftnett, vann og infrastruktur, herunder eierskap av aksjer eller andeler i andre selskaper.”.

Former names: NFH 240611 AS

Key figures · 2025

Operating profit
NOK −2.0m
▼ −301 %
Equity
NOK 6.5bn
▲ +1 %
Est. value
NOK 10.6bn

Financial health · 2025

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

Who owns FARADAY TOPCO AS?

AI VOLT LUXEMBOURG S.A R.L. LU
AI VOLT INVESTMENT & CY S.C.SP LU
FARADAY TOPCO AS
· NOK −2.0m profit

FARADAY TOPCO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FARADAY TOPCO AS own?

FARADAY TOPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FARADAY TOPCO AS

Who owns FARADAY TOPCO AS?

AI VOLT LUXEMBOURG S.A R.L. is the largest registered owner, with 59.3%.

Where is FARADAY TOPCO AS based?

FARADAY TOPCO 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 03.10.2026.

Report a problem

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