BIZTRAC BETA
Computer consultancy and computer facilities management activities

HESSEN INVEST AS

Org. no. 823241852 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 2.8m
Incorporated 2019
Share capital NOK 30,000

Signals

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

HESSEN INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 823241852. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −13,000
Equity
NOK 2.8m
Est. value
NOK 6.7m

Financial health · 2025

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

Who owns HESSEN INVEST AS?

HANS-OLAV HESSEN
HESSEN INVEST AS
· NOK −13,000 profit

HESSEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HESSEN INVEST AS own?

HESSEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HESSEN INVEST AS

Who owns HESSEN INVEST AS?

HANS-OLAV HESSEN is the largest registered owner, with 50.0%.

Who is the general manager of HESSEN INVEST AS?

Hans-Olav Hessen is registered as general manager of HESSEN INVEST AS.

Where is HESSEN INVEST AS based?

HESSEN INVEST AS has its business address in Tolvsrød.

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.