BIZTRAC BETA
Repair and maintenance of motor vehicles

SOMMERSETH AS

Org. no. 921368909 Limited company (AS) Narvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 244.8m
Operating profit NOK 1.4m
Equity NOK 21.1m
Incorporated 2018
Employees 57
Share capital NOK 450,000

SOMMERSETH AS is registered as a limited company in Narvik, Nordland with organisation number 921368909. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2018 and has 57 registered employees. Registered share capital is NOK 450,000, divided into 30 shares. The company's stated purpose is: “Handel og verksteddrift samt hva hermed står i forbindelse, herunder delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 244.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 244.8m
Operating profit
NOK 1.4m
Equity
NOK 21.1m
Est. value
NOK 14.2m

Financial health · 2024

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

Who owns SOMMERSETH AS?

SOMMEREIENDOM HOLDING AS
SOMMERSETH AS
NOK 244.8m rev. · NOK 1.4m profit

SOMMERSETH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOMMERSETH AS own?

SOMMERSETH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOMMERSETH AS

Who owns SOMMERSETH AS?

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

What is the revenue of SOMMERSETH AS?

SOMMERSETH AS had revenue of NOK 244.8m in 2024.

Who is the general manager of SOMMERSETH AS?

Bård Sommerseth is registered as general manager of SOMMERSETH AS.

Where is SOMMERSETH AS based?

SOMMERSETH AS has its business address in Ankenes.

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.