BIZTRAC BETA
Activities of insurance agents and brokers

LEGAL INSURANCE GROUP AS

Org. no. 995727153 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 1.1m
Equity NOK 1.5m
Incorporated 2010
Share capital NOK 1.0m

LEGAL INSURANCE GROUP AS is registered as a limited company in Oslo, Oslo with organisation number 995727153. The business is classified under activities of insurance agents and brokers (NACE 66.220). The company was incorporated in 2010. Registered share capital is NOK 1.0m, divided into 100000 shares. The company's stated purpose is: “Forsikringsagentvirksomhet. Selskapets formål er å drive agent- og multiagenturvirksomhet, herunder annen virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 1.1m
Equity
NOK 1.5m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns LEGAL INSURANCE GROUP AS?

KORSHAMN EFTF. AS
LEGAL INSURANCE GROUP AS
NOK 5.2m rev. · NOK 1.1m profit

LEGAL INSURANCE GROUP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEGAL INSURANCE GROUP AS

Who owns LEGAL INSURANCE GROUP AS?

KORSHAMN EFTF. AS is the largest registered owner, with 65.0%.

What is the revenue of LEGAL INSURANCE GROUP AS?

LEGAL INSURANCE GROUP AS had revenue of NOK 5.2m in 2024.

Who is the general manager of LEGAL INSURANCE GROUP AS?

Silje Merethe Aune Gammelli is registered as general manager of LEGAL INSURANCE GROUP AS.

Where is LEGAL INSURANCE GROUP AS based?

LEGAL INSURANCE GROUP 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.