biztrac. BETA
COMPANY REGISTER PROFILE
998229782 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other investment companies, except captive companies

TOLUMA KREDITT AS

Org. no. 998229782 Limited company (AS) Bærum Incorporated 2012 Active
Revenue 2025 NOK 65.6m
Operating profit NOK 55.0m
Equity NOK 578.3m
Incorporated 2012
Share capital NOK 5.8m

TOLUMA KREDITT AS is registered as a limited company in Bærum, Akershus with organisation number 998229782. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2012. Registered share capital is NOK 5.8m, divided into 5800000 shares. The company's stated purpose is: “Eie og forvalte aksjer, verdipapirer og andre formuesverdier av hvilken som helst art, som inngår i en diversifisert portefølje av hovedsakelig renteinstrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 65.6m in revenue and NOK 55.0m in operating profit.

Key figures · 2025

Revenue
NOK 65.6m
▲ +43 %
Operating profit
NOK 55.0m
▲ +258 %
Equity
NOK 578.3m
▼ −15 %
Est. value
NOK 452.5m

Financial health · 2025

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

Who owns TOLUMA KREDITT AS?

TOLUMA KREDITT AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does TOLUMA KREDITT AS own?

TOLUMA KREDITT AS holds stakes in 34 companies:

See the full ownership structure →

Frequently asked questions about TOLUMA KREDITT AS

Who owns TOLUMA KREDITT AS?

AS CETUS is the largest registered owner, with 26.5%.

What is the revenue of TOLUMA KREDITT AS?

TOLUMA KREDITT AS had revenue of NOK 65.6m in 2025.

Where is TOLUMA KREDITT AS based?

TOLUMA KREDITT 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 03.10.2026.

Report a problem

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