BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ELNESVÅGEN LAVPRIS AS

Org. no. 986081321 Limited company (AS) Hustadvika Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 48.7m
Operating profit NOK 308,000
Equity NOK 6.9m
Incorporated 2003
Employees 22
Share capital NOK 200,000

ELNESVÅGEN LAVPRIS AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 986081321. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2003 and has 22 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drive handel med dagligvarer samt alt som står i forbindelse med dette, her under deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.7m in revenue and NOK 308,000 in operating profit.

Key figures · 2024

Revenue
NOK 48.7m
Operating profit
NOK 308,000
Equity
NOK 6.9m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns ELNESVÅGEN LAVPRIS AS?

No shareholders are registered for ELNESVÅGEN LAVPRIS AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ELNESVÅGEN LAVPRIS AS

What is the revenue of ELNESVÅGEN LAVPRIS AS?

ELNESVÅGEN LAVPRIS AS had revenue of NOK 48.7m in 2024.

Who is the general manager of ELNESVÅGEN LAVPRIS AS?

Marit Indergård Kopstad is registered as general manager of ELNESVÅGEN LAVPRIS AS.

Where is ELNESVÅGEN LAVPRIS AS based?

ELNESVÅGEN LAVPRIS AS has its business address in Elnesvågen.

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.