BIZTRAC BETA
Other personal service activities n.e.c.

DINE HENDER AS

Org. no. 813268892 Limited company (AS) Lier Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 693,000
Operating profit NOK −193,000
Equity NOK −33,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−33k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−193k kr).

DINE HENDER AS is registered as a limited company in Lier, Buskerud with organisation number 813268892. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Negledesign, aromaterapi og salg av varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 693,000 in revenue and NOK −193,000 in operating profit.

Key figures · 2024

Revenue
NOK 693,000
Operating profit
NOK −193,000
Equity
NOK −33,000

Financial health · 2024

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

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

Who owns DINE HENDER AS?

Maria Justad Halden
DINE HENDER AS
NOK 693,000 rev. · NOK −193,000 profit

DINE HENDER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DINE HENDER AS

Who owns DINE HENDER AS?

Maria Justad Halden is the largest registered owner, with 100.0%.

What is the revenue of DINE HENDER AS?

DINE HENDER AS had revenue of NOK 693,000 in 2024.

Who is the general manager of DINE HENDER AS?

Maria Justad Halden is registered as general manager of DINE HENDER AS.

Where is DINE HENDER AS based?

DINE HENDER AS has its business address in Lier.

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.