BIZTRAC BETA
Industrial product and fashion design activities

HELSESENG AS

Org. no. 930248452 Limited company (AS) Aurskog-Høland Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 194,000
Operating profit NOK −77,000
Equity NOK −167,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

HELSESENG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 930248452. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Utvikling av helseseng. Samt det som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 194,000 in revenue and NOK −77,000 in operating profit.

Key figures · 2025

Revenue
NOK 194,000
Operating profit
NOK −77,000
Equity
NOK −167,000

Financial health · 2025

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

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

Who owns HELSESENG AS?

DANIEL EKEBERG AS
HELSESENG AS
NOK 194,000 rev. · NOK −77,000 profit

HELSESENG AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELSESENG AS

Who owns HELSESENG AS?

DANIEL EKEBERG AS is the largest registered owner, with 72.5%.

What is the revenue of HELSESENG AS?

HELSESENG AS had revenue of NOK 194,000 in 2025.

Where is HELSESENG AS based?

HELSESENG AS has its business address in Bjørkelangen.

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.