BIZTRAC BETA
Uoppgitt

H92 HOLDING AS

Org. no. 926282387 Limited company (AS) Stange Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 330,000

Signals

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

H92 HOLDING AS is registered as a limited company in Stange, Innlandet with organisation number 926282387. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 330,000, divided into 3000 shares. The company's stated purpose is: “Å være et holdingselskap. Investeringer i aksjer og øvrige verdipapirer, eiendom og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 1.2m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns H92 HOLDING AS?

PER ERIK FINSTAD
H92 HOLDING AS
NOK 0 rev. · NOK −24,000 profit

H92 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does H92 HOLDING AS own?

H92 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about H92 HOLDING AS

Who owns H92 HOLDING AS?

PER ERIK FINSTAD is the largest registered owner, with 100.0%.

What is the revenue of H92 HOLDING AS?

H92 HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of H92 HOLDING AS?

Per Erik Finstad is registered as general manager of H92 HOLDING AS.

Where is H92 HOLDING AS based?

H92 HOLDING AS has its business address in Ottestad.

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.