BIZTRAC BETA
COMPANY REGISTER PROFILE
826866152 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

HERO HOLDING AS

Org. no. 826866152 Limited company (AS) Oppdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −33,000
Equity NOK 1.2m
Incorporated 2021
Share capital NOK 30,000

Signals

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

HERO HOLDING AS is registered as a limited company in Oppdal, Trøndelag with organisation number 826866152. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Investering og utvikling av eiendom, samt investering i selskaper og annen investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −33,000
▼ −32 %
Equity
NOK 1.2m
▲ +0 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
4.14
Very good
Current assets ÷ current liabilities
Profitability
7.6%
Satisfactory
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns HERO HOLDING AS?

HERO HOLDING AS
NOK 0 rev. · NOK −33,000 profit

HERO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HERO HOLDING AS own?

HERO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HERO HOLDING AS

Who owns HERO HOLDING AS?

ROBERT HOEL is the largest registered owner, with 100.0%.

What is the revenue of HERO HOLDING AS?

HERO HOLDING AS had revenue of NOK 0 in 2025.

Where is HERO HOLDING AS based?

HERO HOLDING AS has its business address in Oppdal.

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

Report a problem

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