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

GRAVDAL DAGLIGVARER AS

Org. no. 824693102 Limited company (AS) Vestvågøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 52.1m
Operating profit NOK 1.8m
Equity NOK 1.0m
Incorporated 2020
Employees 17
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRAVDAL DAGLIGVARER AS is registered as a limited company in Vestvågøy, Nordland with organisation number 824693102. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2020 and has 17 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Drive dagligvarehandel.”. The most recent filed accounts, for the 2024 financial year, show NOK 52.1m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 52.1m
Operating profit
NOK 1.8m
Equity
NOK 1.0m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns GRAVDAL DAGLIGVARER AS?

P KARLSEN INVEST AS
GRAVDAL DAGLIGVARER AS
NOK 52.1m rev. · NOK 1.8m profit

GRAVDAL DAGLIGVARER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRAVDAL DAGLIGVARER AS

Who owns GRAVDAL DAGLIGVARER AS?

P KARLSEN INVEST AS is the largest registered owner, with 70.0%.

What is the revenue of GRAVDAL DAGLIGVARER AS?

GRAVDAL DAGLIGVARER AS had revenue of NOK 52.1m in 2024.

Where is GRAVDAL DAGLIGVARER AS based?

GRAVDAL DAGLIGVARER AS has its business address in Gravdal.

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.