biztrac. BETA
COMPANY REGISTER PROFILE
940231531 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Administration of financial markets

BANKENES SIKRINGSFOND

Org. no. 940231531 Other business enterprise in accordance with special legislation (SÆR) Oslo Incorporated 1970 Active
Ownership graph ↗
Revenue 2025 NOK 2.9bn
Operating profit NOK 2.8bn
Equity NOK 60.0bn
Incorporated 1970
Employees 22

BANKENES SIKRINGSFOND is registered as a other business enterprise in accordance with special legislation in Oslo, Oslo with organisation number 940231531. The business is classified under administration of financial markets (NACE 66.110). The company was incorporated in 1970 and has 22 registered employees. The company's stated purpose is: “Oppgaver som nærmere angitt i lov om Bankenes sikringsfond § 2.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9bn in revenue and NOK 2.8bn in operating profit.

Former names: SPAREBANKENES SIKRINGSFOND

Key figures · 2025

Revenue
NOK 2.9bn
▲ +3 %
Operating profit
NOK 2.8bn
▲ +3 %
Equity
NOK 60.0bn
▲ +10 %
Est. value
NOK 41.3bn

Financial health · 2025

Liquidity
178.86
Very good
Current assets ÷ current liabilities
Profitability
9.1%
Satisfactory
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns BANKENES SIKRINGSFOND?

No shareholders are registered for BANKENES SIKRINGSFOND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BANKENES SIKRINGSFOND

What is the revenue of BANKENES SIKRINGSFOND?

BANKENES SIKRINGSFOND had revenue of NOK 2.9bn in 2025.

Who is the general manager of BANKENES SIKRINGSFOND?

Sonja Lill Flø Myklebust is registered as general manager of BANKENES SIKRINGSFOND.

Where is BANKENES SIKRINGSFOND based?

BANKENES SIKRINGSFOND 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.