BIZTRAC BETA
Research and experimental development on natural sciences and engineering

VIRIDIH2 AS

Org. no. 931908774 Limited company (AS) Rendalen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −36,000
Equity NOK 33,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VIRIDIH2 AS is registered as a limited company in Rendalen, Innlandet with organisation number 931908774. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal utvikle og kommersialisere produksjon av hydrogen samt produkter og tjenester knyttet til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −36,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −36,000
Equity
NOK 33,000
Est. value
NOK 54,000

Financial health · 2024

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

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

Who owns VIRIDIH2 AS?

NAPOP AS
VIRIDIH2 AS
NOK 0 rev. · NOK −36,000 profit

VIRIDIH2 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIRIDIH2 AS own?

VIRIDIH2 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIRIDIH2 AS

Who owns VIRIDIH2 AS?

NAPOP AS is the largest registered owner, with 100.0%.

What is the revenue of VIRIDIH2 AS?

VIRIDIH2 AS had revenue of NOK 0 in 2024.

Where is VIRIDIH2 AS based?

VIRIDIH2 AS has its business address in Rendalen.

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.