BIZTRAC BETA
Activities of insurance agents and brokers

VIKING ASSISTANCE AS

Org. no. 815687132 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 26.6m
Operating profit NOK 15.5m
Equity NOK 26.4m
Incorporated 2015
Share capital NOK 60,000

VIKING ASSISTANCE AS is registered as a limited company in Oslo, Oslo with organisation number 815687132. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2015. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Markedsføre og selge forsikringer for bilbergingstjenester til sluttbrukere i Norge som en forsikringsformidler. Selskapet skal ikke drive egen bilbergingstjeneste eller kundesenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.6m in revenue and NOK 15.5m in operating profit.

Key figures · 2024

Revenue
NOK 26.6m
Operating profit
NOK 15.5m
Equity
NOK 26.4m
Est. value
NOK 56.0m

Financial health · 2024

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

Who owns VIKING ASSISTANCE AS?

VIKING REDNINGSTJENESTE AS
VIKING ASSISTANCE AS
NOK 26.6m rev. · NOK 15.5m profit

VIKING ASSISTANCE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKING ASSISTANCE AS

Who owns VIKING ASSISTANCE AS?

VIKING REDNINGSTJENESTE AS is the largest registered owner, with 100.0%.

What is the revenue of VIKING ASSISTANCE AS?

VIKING ASSISTANCE AS had revenue of NOK 26.6m in 2024.

Who is the general manager of VIKING ASSISTANCE AS?

Olof Mårten Rosman is registered as general manager of VIKING ASSISTANCE AS.

Where is VIKING ASSISTANCE AS based?

VIKING ASSISTANCE 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.