BIZTRAC BETA
Computer consultancy and computer facilities management activities

JA HATLELID HOLDING AS

Org. no. 924393289 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 3.1m
Incorporated 2020
Share capital NOK 30,000

Signals

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

JA HATLELID HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 924393289. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer, samt investeringer i virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 3.1m
Est. value
NOK 14.0m

Financial health · 2025

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

Who owns JA HATLELID HOLDING AS?

JØRN ARE HATLELID
JA HATLELID HOLDING AS
NOK 0 rev. · NOK −2,000 profit

JA HATLELID HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JA HATLELID HOLDING AS own?

JA HATLELID HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JA HATLELID HOLDING AS

Who owns JA HATLELID HOLDING AS?

JØRN ARE HATLELID is the largest registered owner, with 100.0%.

What is the revenue of JA HATLELID HOLDING AS?

JA HATLELID HOLDING AS had revenue of NOK 0 in 2025.

Where is JA HATLELID HOLDING AS based?

JA HATLELID HOLDING AS has its business address in Oslo.

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.