BIZTRAC BETA
Computer programming activities

HIRO AS

Org. no. 821446422 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK −2.8m
Equity NOK −2.2m
Incorporated 2018
Employees 7
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,8 mill kr).
  • Nylig endring 2026-07-03 Aksjekapital registrert 2026-07-03.

HIRO AS is registered as a limited company in Oslo, Oslo with organisation number 821446422. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive utvikling, produksjon og salg av teknologibaserte produkter og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK −2.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK −2.8m
Equity
NOK −2.2m

Financial health · 2024

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

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

Who owns HIRO AS?

MASMASMAS AS
HIRO AS
NOK 2.8m rev. · NOK −2.8m profit

HIRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HIRO AS

Who owns HIRO AS?

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

What is the revenue of HIRO AS?

HIRO AS had revenue of NOK 2.8m in 2024.

Who is the general manager of HIRO AS?

Silje Gabrielsen is registered as general manager of HIRO AS.

Where is HIRO AS based?

HIRO AS has its business address in Oslo.

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.