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

HEIMSTAD VENTURE AS

Org. no. 831509902 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −44
Equity NOK −875,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

HEIMSTAD VENTURE AS is registered as a limited company in Bærum, Akershus with organisation number 831509902. 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: “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 −44
▲ +99 %
Equity
NOK −875,000
▼ −133 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
-175.8%
Weak
Equity as a share of total capital

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

Who owns HEIMSTAD VENTURE AS?

HEIMSTAD VENTURE AS
· NOK −44 profit

HEIMSTAD VENTURE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEIMSTAD VENTURE AS own?

HEIMSTAD VENTURE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HEIMSTAD VENTURE AS

Who owns HEIMSTAD VENTURE AS?

Edvin Heimstad is the largest registered owner, with 100.0%.

Where is HEIMSTAD VENTURE AS based?

HEIMSTAD VENTURE AS has its business address in Sandvika.

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.