biztrac. BETA
COMPANY REGISTER PROFILE
931247476 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

KANGAROO FINCO AS

Org. no. 931247476 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit USD −7,000
Equity USD 1.3bn
Incorporated 2023
Share capital NOK 143.7m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

KANGAROO FINCO AS is registered as a limited company in Oslo, Oslo with organisation number 931247476. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 143.7m, divided into 14367674 shares. The company's stated purpose is: “Eie og handle finansielle instrumenter, herunder med aksjer, og alt som står i naturlig forbindelse med dette.”.

Former names: NFH 230434 AS

This company reports in USD. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Operating profit
USD −7,000
▲ +25 %
Equity
USD 1.3bn
▼ −4 %
Est. value
NOK 24.1bn

Financial health · 2025

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

Who owns KANGAROO FINCO AS?

KANGAROO FINCO AS
· NOK −7,000 profit

KANGAROO FINCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KANGAROO FINCO AS own?

KANGAROO FINCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KANGAROO FINCO AS

Who owns KANGAROO FINCO AS?

KANGAROO HOLDCO AS is the largest registered owner, with 100.0%.

Where is KANGAROO FINCO AS based?

KANGAROO FINCO 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.