BIZTRAC BETA
Activities of insurance agents and brokers

SØR FORSIKRING AS

Org. no. 990577161 Limited company (AS) Arendal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 14.2m
Operating profit NOK 1.6m
Equity NOK 657,000
Incorporated 2006
Employees 15
Share capital NOK 250,000

SØR FORSIKRING AS is registered as a limited company in Arendal, Agder with organisation number 990577161. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2006 and has 15 registered employees. Registered share capital is NOK 250,000, divided into 2500 shares. The company's stated purpose is: “Salg av forsikrings- og finansprodukter og annen virksomhet forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 14.2m
Operating profit
NOK 1.6m
Equity
NOK 657,000
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns SØR FORSIKRING AS?

SØR ELLINGSEN HOLDING AS
SØR FORSIKRING AS
NOK 14.2m rev. · NOK 1.6m profit

SØR FORSIKRING AS has 3 registered shareholders:

All shareholders and roles →

Group structure

SØR FORSIKRING AS er morselskap for 2 datterselskaper:

Frequently asked questions about SØR FORSIKRING AS

Who owns SØR FORSIKRING AS?

SØR ELLINGSEN HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of SØR FORSIKRING AS?

SØR FORSIKRING AS had revenue of NOK 14.2m in 2025.

Who is the general manager of SØR FORSIKRING AS?

Henning Oskar Ellingsen is registered as general manager of SØR FORSIKRING AS.

Where is SØR FORSIKRING AS based?

SØR FORSIKRING AS has its business address in Arendal.

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.