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

HALSA DAGLIGVARE AS

Org. no. 918627758 Limited company (AS) Heim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 25.8m
Operating profit NOK 1.0m
Equity NOK 1.5m
Incorporated 2017
Employees 16
Share capital NOK 600,000

HALSA DAGLIGVARE AS is registered as a limited company in Heim, Trøndelag with organisation number 918627758. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2017 and has 16 registered employees. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Butikkhandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 25.8m
Operating profit
NOK 1.0m
Equity
NOK 1.5m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns HALSA DAGLIGVARE AS?

UMBRELLA CORP AS
HALSA DAGLIGVARE AS
NOK 25.8m rev. · NOK 1.0m profit

HALSA DAGLIGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALSA DAGLIGVARE AS

Who owns HALSA DAGLIGVARE AS?

UMBRELLA CORP AS is the largest registered owner, with 100.0%.

What is the revenue of HALSA DAGLIGVARE AS?

HALSA DAGLIGVARE AS had revenue of NOK 25.8m in 2024.

Who is the general manager of HALSA DAGLIGVARE AS?

Torstein Krumsvik Hyldbakk is registered as general manager of HALSA DAGLIGVARE AS.

Where is HALSA DAGLIGVARE AS based?

HALSA DAGLIGVARE AS has its business address in Halsanaustan.

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.