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

R.A.D. DAGLIGVARE AS

Org. no. 987564989 Limited company (AS) Drammen Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 80.8m
Operating profit NOK 1.9m
Equity NOK 901,000
Incorporated 2004
Employees 17
Share capital NOK 350,000

R.A.D. DAGLIGVARE AS is registered as a limited company in Drammen, Buskerud with organisation number 987564989. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2004 and has 17 registered employees. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Dagligvarehandel, handel og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 80.8m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 80.8m
Operating profit
NOK 1.9m
Equity
NOK 901,000
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns R.A.D. DAGLIGVARE AS?

RUNE ANDRE DAHLBERG
R.A.D. DAGLIGVARE AS
NOK 80.8m rev. · NOK 1.9m profit

R.A.D. DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R.A.D. DAGLIGVARE AS

Who owns R.A.D. DAGLIGVARE AS?

RUNE ANDRE DAHLBERG is the largest registered owner, with 100.0%.

What is the revenue of R.A.D. DAGLIGVARE AS?

R.A.D. DAGLIGVARE AS had revenue of NOK 80.8m in 2025.

Who is the general manager of R.A.D. DAGLIGVARE AS?

Rune Andre Dahlberg is registered as general manager of R.A.D. DAGLIGVARE AS.

Where is R.A.D. DAGLIGVARE AS based?

R.A.D. DAGLIGVARE AS has its business address in Drammen.

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.