BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

FORSIKRINGSTAKST AS

Org. no. 931944789 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 29.6m
Operating profit NOK 4.8m
Equity NOK 4.2m
Incorporated 2023
Share capital NOK 30,000

FORSIKRINGSTAKST AS is registered as a limited company in Oslo, Oslo with organisation number 931944789. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Skade- og verdivurdering av kjøretøy samt teknisk konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.6m in revenue and NOK 4.8m in operating profit.

Key figures · 2025

Revenue
NOK 29.6m
Operating profit
NOK 4.8m
Equity
NOK 4.2m
Est. value
NOK 25.4m

Financial health · 2025

Liquidity
1.69
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.9%
Very good
Equity as a share of total capital

Who owns FORSIKRINGSTAKST AS?

LØKEN HOLDING AS
FORSIKRINGSTAKST AS
NOK 29.6m rev. · NOK 4.8m profit

FORSIKRINGSTAKST AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FORSIKRINGSTAKST AS er morselskap for 1 datterselskap:

Frequently asked questions about FORSIKRINGSTAKST AS

Who owns FORSIKRINGSTAKST AS?

LØKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FORSIKRINGSTAKST AS?

FORSIKRINGSTAKST AS had revenue of NOK 29.6m in 2025.

Who is the general manager of FORSIKRINGSTAKST AS?

Lars Jørgen Løken is registered as general manager of FORSIKRINGSTAKST AS.

Where is FORSIKRINGSTAKST AS based?

FORSIKRINGSTAKST AS has its business address in Oslo.

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.