biztrac. BETA
COMPANY REGISTER PROFILE
929119088 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HELTIVATER INVEST AS

Org. no. 929119088 Limited company (AS) Horten Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −9,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

HELTIVATER INVEST AS is registered as a limited company in Horten, Vestfold with organisation number 929119088. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. 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 −9,000
▼ −32 %
Equity
NOK −9,000
▼ −616 %

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
-41.4%
Not satisfactory
Return on total assets
Solidity
-119.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HELTIVATER INVEST AS?

HELTIVATER INVEST AS
· NOK −9,000 profit

HELTIVATER INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELTIVATER INVEST AS

Who owns HELTIVATER INVEST AS?

Kay Hansen is the largest registered owner, with 100.0%.

Who is the general manager of HELTIVATER INVEST AS?

Kay Hansen is registered as general manager of HELTIVATER INVEST AS.

Where is HELTIVATER INVEST AS based?

HELTIVATER INVEST AS has its business address in Horten.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.