BIZTRAC BETA
Retail sale of motor vehicles

HENGER.NO

Org. no. 914994039 Limited company (AS) Nes Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 20.7m
Operating profit NOK −653,000
Equity NOK 1.2m
Incorporated 2014
Share capital NOK 60,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−653k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-14 Aksjekapital registrert 2026-04-14.

HENGER.NO is registered as a limited company in Nes, Akershus with organisation number 914994039. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2014. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge motorvogner, hengere mv, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.7m in revenue and NOK −653,000 in operating profit.

Key figures · 2024

Revenue
NOK 20.7m
Operating profit
NOK −653,000
Equity
NOK 1.2m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns HENGER.NO?

NORSKE HOLDING AS
HENGER.NO
NOK 20.7m rev. · NOK −653,000 profit

HENGER.NO has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENGER.NO

Who owns HENGER.NO?

NORSKE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HENGER.NO?

HENGER.NO had revenue of NOK 20.7m in 2024.

Who is the general manager of HENGER.NO?

Kjell Jevne is registered as general manager of HENGER.NO.

Where is HENGER.NO based?

HENGER.NO has its business address in Årnes.

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.