BIZTRAC BETA
Activities of insurance agents and brokers

LIVING FORSIKRING AS

Org. no. 912531678 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 1.6m
Equity NOK 138,000
Incorporated 2013
Employees 8
Share capital NOK 30,000

LIVING FORSIKRING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 912531678. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2013 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Formidling av produkter og løsninger mot skade og livsforsikringer, pensjon og finansieringsløsninger og ikke konsesjonsbelagte spareprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 1.6m
Equity
NOK 138,000
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns LIVING FORSIKRING AS?

VIVERE HOLDING AS
LIVING FORSIKRING AS
NOK 8.5m rev. · NOK 1.6m profit

LIVING FORSIKRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIVING FORSIKRING AS

Who owns LIVING FORSIKRING AS?

VIVERE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIVING FORSIKRING AS?

LIVING FORSIKRING AS had revenue of NOK 8.5m in 2024.

Who is the general manager of LIVING FORSIKRING AS?

Per Kristian Aas is registered as general manager of LIVING FORSIKRING AS.

Where is LIVING FORSIKRING AS based?

LIVING FORSIKRING AS has its business address in Tønsberg.

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.