BIZTRAC BETA
Retail sale of other food

NORSK HELSEKOST AS

Org. no. 933838978 Limited company (AS) Asker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 5,000
Operating profit NOK −34,000
Equity NOK −13,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−13k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).

NORSK HELSEKOST AS is registered as a limited company in Asker, Akershus with organisation number 933838978. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Postordre-/internetthandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 5,000 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 5,000
Operating profit
NOK −34,000
Equity
NOK −13,000

Financial health · 2025

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

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

Who owns NORSK HELSEKOST AS?

MICHAEL RISNES
NORSK HELSEKOST AS
NOK 5,000 rev. · NOK −34,000 profit

NORSK HELSEKOST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK HELSEKOST AS

Who owns NORSK HELSEKOST AS?

MICHAEL RISNES is the largest registered owner, with 33.3%.

What is the revenue of NORSK HELSEKOST AS?

NORSK HELSEKOST AS had revenue of NOK 5,000 in 2025.

Who is the general manager of NORSK HELSEKOST AS?

Simen Mjåset is registered as general manager of NORSK HELSEKOST AS.

Where is NORSK HELSEKOST AS based?

NORSK HELSEKOST AS has its business address in Heggedal.

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.