BIZTRAC BETA
Uoppgitt

HATAWI AS

Org. no. 932396459 Limited company (AS) Harstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −14,000
Equity NOK 2.1m
Incorporated 2023
Share capital NOK 2.2m

Signals

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

HATAWI AS is registered as a limited company in Harstad, Troms with organisation number 932396459. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 2.2m, divided into 22200 shares. The company's stated purpose is: “Forvaltning av personlig formue ved finansielle plasseringer, investeringer og andre produkter/tjenester som naturlig hører sammen med dette , herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK −14,000
Equity
NOK 2.1m
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
46177.33
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 HATAWI AS?

HÅKON TANDSTAD WIBE
HATAWI AS
NOK 6,000 rev. · NOK −14,000 profit

HATAWI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HATAWI AS own?

HATAWI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HATAWI AS

Who owns HATAWI AS?

HÅKON TANDSTAD WIBE is the largest registered owner, with 100.0%.

What is the revenue of HATAWI AS?

HATAWI AS had revenue of NOK 6,000 in 2025.

Where is HATAWI AS based?

HATAWI AS has its business address in Harstad.

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.