BIZTRAC BETA
Freight transport by road

HANS ASK HOLDING AS

Org. no. 989215175 Limited company (AS) Gjerdrum Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −54,000
Equity NOK 7.4m
Incorporated 2005
Share capital NOK 2.9m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HANS ASK HOLDING AS is registered as a limited company in Gjerdrum, Akershus with organisation number 989215175. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 170 shares. The company's stated purpose is: “Kjøp, salg og vedlikehold av industrimaskiner. Investering, kjøp og salg av verdipapirer og aksjer i andre selskaper samt alt som hører naturlig til disse områdene.”.

Key figures · 2024

Operating profit
NOK −54,000
Equity
NOK 7.4m
Est. value
NOK 7.9m

Financial health · 2024

Liquidity
33.41
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.2%
Very good
Equity as a share of total capital

Who owns HANS ASK HOLDING AS?

HANS KRISTIAN ASK
HANS ASK HOLDING AS
· NOK −54,000 profit

HANS ASK HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HANS ASK HOLDING AS own?

HANS ASK HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HANS ASK HOLDING AS

Who owns HANS ASK HOLDING AS?

HANS KRISTIAN ASK is the largest registered owner, with 84.7%.

Who is the general manager of HANS ASK HOLDING AS?

Hans Kristian Ask is registered as general manager of HANS ASK HOLDING AS.

Where is HANS ASK HOLDING AS based?

HANS ASK HOLDING AS has its business address in Gjerdrum.

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.