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

EIDSNES DAGLIGVARER AS

Org. no. 999614868 Limited company (AS) Sula Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 53.7m
Operating profit NOK 2.3m
Equity NOK 5.6m
Incorporated 2013
Employees 29
Share capital NOK 3.0m

EIDSNES DAGLIGVARER AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 999614868. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2013 and has 29 registered employees. Registered share capital is NOK 3.0m, divided into 100 shares. The company's stated purpose is: “Å organisere dagligvareforretning og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 53.7m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 53.7m
Operating profit
NOK 2.3m
Equity
NOK 5.6m
Est. value
NOK 11.6m

Financial health · 2024

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.6%
Very good
Equity as a share of total capital

Who owns EIDSNES DAGLIGVARER AS?

PÅL ANDRÉ LUNDBØ
EIDSNES DAGLIGVARER AS
NOK 53.7m rev. · NOK 2.3m profit

EIDSNES DAGLIGVARER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIDSNES DAGLIGVARER AS

Who owns EIDSNES DAGLIGVARER AS?

PÅL ANDRÉ LUNDBØ is the largest registered owner, with 50.0%.

What is the revenue of EIDSNES DAGLIGVARER AS?

EIDSNES DAGLIGVARER AS had revenue of NOK 53.7m in 2024.

Who is the general manager of EIDSNES DAGLIGVARER AS?

Tor Erik Voldsund is registered as general manager of EIDSNES DAGLIGVARER AS.

Where is EIDSNES DAGLIGVARER AS based?

EIDSNES DAGLIGVARER AS has its business address in Eidsnes.

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.