BIZTRAC BETA
Repair and maintenance of motor vehicles

STOREMYRSLETTA 2 AS

Org. no. 943558604 Limited company (AS) Lillesand Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.1m
Equity NOK 7.8m
Incorporated 1987
Share capital NOK 100,000

STOREMYRSLETTA 2 AS is registered as a limited company in Lillesand, Agder with organisation number 943558604. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1987. Registered share capital is NOK 100,000. The company's stated purpose is: “Utvikling, utleie og salg av fast eiendom, investere i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.1m
Equity
NOK 7.8m
Est. value
NOK 6.5m

Financial health · 2024

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

Who owns STOREMYRSLETTA 2 AS?

NUMMER 23 AS
STOREMYRSLETTA 2 AS
NOK 1.7m rev. · NOK 1.1m profit

STOREMYRSLETTA 2 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STOREMYRSLETTA 2 AS own?

STOREMYRSLETTA 2 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STOREMYRSLETTA 2 AS

Who owns STOREMYRSLETTA 2 AS?

NUMMER 23 AS is the largest registered owner, with 90.1%.

What is the revenue of STOREMYRSLETTA 2 AS?

STOREMYRSLETTA 2 AS had revenue of NOK 1.7m in 2024.

Who is the general manager of STOREMYRSLETTA 2 AS?

Svein Tore Aanonsen is registered as general manager of STOREMYRSLETTA 2 AS.

Where is STOREMYRSLETTA 2 AS based?

STOREMYRSLETTA 2 AS has its business address in Lillesand.

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.