BIZTRAC BETA
Activities of insurance agents and brokers

BÆRUM FORSIKRINGSSENTER AS

Org. no. 912397378 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 14.9m
Operating profit NOK 1.7m
Equity NOK 182,000
Incorporated 2013
Employees 13
Share capital NOK 30,000

BÆRUM FORSIKRINGSSENTER AS is registered as a limited company in Bærum, Akershus with organisation number 912397378. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2013 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og service av forsikringer, samt investere i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.9m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 14.9m
Operating profit
NOK 1.7m
Equity
NOK 182,000
Est. value
NOK 4.5m

Financial health · 2025

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.2%
Weak
Equity as a share of total capital

Who owns BÆRUM FORSIKRINGSSENTER AS?

VARSI HOLDING AS
BÆRUM FORSIKRINGSSENTER AS
NOK 14.9m rev. · NOK 1.7m profit

BÆRUM FORSIKRINGSSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÆRUM FORSIKRINGSSENTER AS

Who owns BÆRUM FORSIKRINGSSENTER AS?

VARSI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BÆRUM FORSIKRINGSSENTER AS?

BÆRUM FORSIKRINGSSENTER AS had revenue of NOK 14.9m in 2025.

Who is the general manager of BÆRUM FORSIKRINGSSENTER AS?

Hans-Ari Ballovara Varsi is registered as general manager of BÆRUM FORSIKRINGSSENTER AS.

Where is BÆRUM FORSIKRINGSSENTER AS based?

BÆRUM FORSIKRINGSSENTER AS has its business address in Rud.

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.