BIZTRAC BETA
Buying and selling of own real estate

HATEK AS

Org. no. 996102157 Limited company (AS) Austevoll Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 417,000
Equity NOK 2.1m
Incorporated 2010
Share capital NOK 100,000

HATEK AS is registered as a limited company in Austevoll, Vestland with organisation number 996102157. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 300 shares. The company's stated purpose is: “Investeringer i verdipapirer og forvaltning av eierinteresse, kjøp, salg, utleie og utvikling av fast eiendom. Selskapet skal også kunne utføre konsulenttjenester innen administrasjon, økonomi, strategi og IT.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 417,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 417,000
Equity
NOK 2.1m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns HATEK AS?

AMUND MØGSTER HATLEVIK
HATEK AS
NOK 1.4m rev. · NOK 417,000 profit

HATEK AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HATEK AS own?

HATEK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HATEK AS

Who owns HATEK AS?

AMUND MØGSTER HATLEVIK is the largest registered owner, with 30.0%.

What is the revenue of HATEK AS?

HATEK AS had revenue of NOK 1.4m in 2024.

Who is the general manager of HATEK AS?

Amund Møgster Hatlevik is registered as general manager of HATEK AS.

Where is HATEK AS based?

HATEK AS has its business address in Storebø.

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.