BIZTRAC BETA
Other captive investment companies

HA-TA HOLDING AS

Org. no. 999328121 Limited company (AS) Sarpsborg Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 3.9m
Incorporated 2012
Share capital NOK 30,000

Signals

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

HA-TA HOLDING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 999328121. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i andre selskap, og investere i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 3.9m
Est. value
NOK 5.4m

Financial health · 2025

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

Who owns HA-TA HOLDING AS?

HELGE ANDREASSEN
HA-TA HOLDING AS
NOK 0 rev. · NOK −20,000 profit

HA-TA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HA-TA HOLDING AS own?

HA-TA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HA-TA HOLDING AS

Who owns HA-TA HOLDING AS?

HELGE ANDREASSEN is the largest registered owner, with 100.0%.

What is the revenue of HA-TA HOLDING AS?

HA-TA HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of HA-TA HOLDING AS?

Helge Andreassen is registered as general manager of HA-TA HOLDING AS.

Where is HA-TA HOLDING AS based?

HA-TA HOLDING AS has its business address in Borgenhaugen.

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.