BIZTRAC BETA
Research and experimental development on natural sciences and engineering

HELIUM 3 AS

Org. no. 997775163 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −90,000
Equity NOK 846,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

HELIUM 3 AS is registered as a limited company in Bærum, Akershus with organisation number 997775163. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive med forskning og utvikling mot mange bransjer, som luftfart, skogsbruk, transport og jernbane. Selskapet skal også levere varer og konsultenttjenester til anleggsbransjen, legemiddelsbransjen, olje og gass og motorsport. I tillegg skal skal selskapet drive med investeringsvirksomhet av enhver art, herunder deltakelse i andre selskaper samt alt som står i forbindelse hermed.”.

Key figures · 2024

Operating profit
NOK −90,000
Equity
NOK 846,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns HELIUM 3 AS?

NIGEL LUDWIG HANSEN
HELIUM 3 AS
· NOK −90,000 profit

HELIUM 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELIUM 3 AS

Who owns HELIUM 3 AS?

NIGEL LUDWIG HANSEN is the largest registered owner, with 100.0%.

Who is the general manager of HELIUM 3 AS?

Nigel Ludwig Hansen is registered as general manager of HELIUM 3 AS.

Where is HELIUM 3 AS based?

HELIUM 3 AS has its business address in Høvik.

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.