BIZTRAC BETA
Uoppgitt

DIN FORSIKRINGSPARTNER AS

Org. no. 988864846 Limited company (AS) Asker Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK −1.0m
Equity NOK 135,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,0 mill kr).

DIN FORSIKRINGSPARTNER AS is registered as a limited company in Asker, Akershus with organisation number 988864846. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av forsikringsløsninger, og det som naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK −1.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK −1.0m
Equity
NOK 135,000
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns DIN FORSIKRINGSPARTNER AS?

ROLF CHRISTIAN KRAUSS
DIN FORSIKRINGSPARTNER AS
NOK 5.1m rev. · NOK −1.0m profit

DIN FORSIKRINGSPARTNER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DIN FORSIKRINGSPARTNER AS

Who owns DIN FORSIKRINGSPARTNER AS?

ROLF CHRISTIAN KRAUSS is the largest registered owner, with 80.0%.

What is the revenue of DIN FORSIKRINGSPARTNER AS?

DIN FORSIKRINGSPARTNER AS had revenue of NOK 5.1m in 2024.

Who is the general manager of DIN FORSIKRINGSPARTNER AS?

Rolf Christian Krauss is registered as general manager of DIN FORSIKRINGSPARTNER AS.

Where is DIN FORSIKRINGSPARTNER AS based?

DIN FORSIKRINGSPARTNER AS has its business address in Hvalstad.

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.