BIZTRAC BETA
Uoppgitt

HATLELID INVEST AS

Org. no. 925512478 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 13.2m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

HATLELID INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 925512478. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investeringsvirksomhet av enhver art, herunder deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 13.2m
Est. value
NOK 72.7m

Financial health · 2024

Liquidity
Not available
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 HATLELID INVEST AS?

EIVIND JOHANNES HATLELID
HATLELID INVEST AS
NOK 0 rev. · NOK −3,000 profit

HATLELID INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HATLELID INVEST AS own?

HATLELID INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HATLELID INVEST AS

Who owns HATLELID INVEST AS?

EIVIND JOHANNES HATLELID is the largest registered owner, with 100.0%.

What is the revenue of HATLELID INVEST AS?

HATLELID INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of HATLELID INVEST AS?

Eivind Johannes Hatlelid is registered as general manager of HATLELID INVEST AS.

Where is HATLELID INVEST AS based?

HATLELID INVEST 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.