BIZTRAC BETA
Activities of insurance agents and brokers

BJØRNHAUG ASSURANSE AS

Org. no. 927150638 Limited company (AS) Nesodden Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 334,000
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

BJØRNHAUG ASSURANSE AS is registered as a limited company in Nesodden, Akershus with organisation number 927150638. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av privatforsikring i Norge på vegne av If Skadeforsikring.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 334,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 334,000
Equity
NOK 30,000
Est. value
NOK 901,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BJØRNHAUG ASSURANSE AS?

KARL ERIK BJØRNHAUG
BJØRNHAUG ASSURANSE AS
NOK 2.2m rev. · NOK 334,000 profit

BJØRNHAUG ASSURANSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJØRNHAUG ASSURANSE AS

Who owns BJØRNHAUG ASSURANSE AS?

KARL ERIK BJØRNHAUG is the largest registered owner, with 100.0%.

What is the revenue of BJØRNHAUG ASSURANSE AS?

BJØRNHAUG ASSURANSE AS had revenue of NOK 2.2m in 2024.

Who is the general manager of BJØRNHAUG ASSURANSE AS?

Karl Erik Bjørnhaug is registered as general manager of BJØRNHAUG ASSURANSE AS.

Where is BJØRNHAUG ASSURANSE AS based?

BJØRNHAUG ASSURANSE AS has its business address in Nesodden.

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.