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

ÅLINGEN DAGLIGVARE AS

Org. no. 936678513 Limited company (AS) Ål Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 29,000
Incorporated 2025
Employees 16
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-11-18.

ÅLINGEN DAGLIGVARE AS is registered as a limited company in Ål, Buskerud with organisation number 936678513. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2025 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 29,000
Est. value
NOK 36,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ÅLINGEN DAGLIGVARE AS?

REMA 1000 NORGE AS
ÅLINGEN DAGLIGVARE AS
· NOK −1,000 profit

ÅLINGEN DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅLINGEN DAGLIGVARE AS

Who owns ÅLINGEN DAGLIGVARE AS?

REMA 1000 NORGE AS is the largest registered owner, with 100.0%.

Who is the general manager of ÅLINGEN DAGLIGVARE AS?

Knut Erik Olsen is registered as general manager of ÅLINGEN DAGLIGVARE AS.

Where is ÅLINGEN DAGLIGVARE AS based?

ÅLINGEN DAGLIGVARE AS has its business address in Ål.

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.