BIZTRAC BETA
Uoppgitt

HAWKHILL INVEST AS

Org. no. 832253502 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 263,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).
  • Nylig endring 2026-04-16 Adresseendring registrert 2026-04-16.

HAWKHILL INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 832253502. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 263,000
Est. value
NOK 309,000

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 HAWKHILL INVEST AS?

JØRGEN HAUKÅS
HAWKHILL INVEST AS
NOK 0 rev. · NOK −2,000 profit

HAWKHILL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAWKHILL INVEST AS own?

HAWKHILL INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HAWKHILL INVEST AS

Who owns HAWKHILL INVEST AS?

JØRGEN HAUKÅS is the largest registered owner, with 100.0%.

What is the revenue of HAWKHILL INVEST AS?

HAWKHILL INVEST AS had revenue of NOK 0 in 2024.

Where is HAWKHILL INVEST AS based?

HAWKHILL 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.