biztrac. BETA
COMPANY REGISTER PROFILE
936327249 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

HANG-ON AS

Org. no. 936327249 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 51,000
Operating profit NOK −5,000
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

HANG-ON AS is registered as a limited company in Larvik, Vestfold with organisation number 936327249. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive butikkhandel og netthandel av bil og båt hengere, tilhørende tilbehør og reservedeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 51,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK −5,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

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

Who owns HANG-ON AS?

HANG-ON AS
NOK 51,000 rev. · NOK −5,000 profit

HANG-ON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HANG-ON AS

Who owns HANG-ON AS?

Richard Scott Cartwright is the largest registered owner, with 50.0%.

What is the revenue of HANG-ON AS?

HANG-ON AS had revenue of NOK 51,000 in 2025.

Who is the general manager of HANG-ON AS?

Rune Lyngby is registered as general manager of HANG-ON AS.

Where is HANG-ON AS based?

HANG-ON AS has its business address in Tjodalyng.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.