BIZTRAC BETA
Activities of insurance agents and brokers

FORSIKRINGSHUSET RINGERIKE AS

Org. no. 912304752 Limited company (AS) Ringerike Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 787,000
Equity NOK 986,000
Incorporated 2013
Employees 5
Share capital NOK 60,000

FORSIKRINGSHUSET RINGERIKE AS is registered as a limited company in Ringerike, Buskerud with organisation number 912304752. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Salg av forsikringstjenester og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 787,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 787,000
Equity
NOK 986,000

Who owns FORSIKRINGSHUSET RINGERIKE AS?

Anders Kozak Høibråten
FORSIKRINGSHUSET RINGERIKE AS
NOK 6.5m rev. · NOK 787,000 profit

FORSIKRINGSHUSET RINGERIKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FORSIKRINGSHUSET RINGERIKE AS

Who owns FORSIKRINGSHUSET RINGERIKE AS?

Anders Kozak Høibråten is the largest registered owner, with 50.0%.

What is the revenue of FORSIKRINGSHUSET RINGERIKE AS?

FORSIKRINGSHUSET RINGERIKE AS had revenue of NOK 6.5m in 2025.

Who is the general manager of FORSIKRINGSHUSET RINGERIKE AS?

Anders Kozak Høibråten is registered as general manager of FORSIKRINGSHUSET RINGERIKE AS.

Where is FORSIKRINGSHUSET RINGERIKE AS based?

FORSIKRINGSHUSET RINGERIKE AS has its business address in Hønefoss.

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.