BIZTRAC BETA
COMPANY REGISTER PROFILE
928354555 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HERI HOLDING AS

Org. no. 928354555 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 37,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

HERI HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 928354555. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 37,000
Est. value
NOK 44,000

Financial health · 2025

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

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

Who owns HERI HOLDING AS?

HERI HOLDING AS
· NOK −3,000 profit

HERI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HERI HOLDING AS

Who owns HERI HOLDING AS?

HEGE RINGDAL is the largest registered owner, with 100.0%.

Where is HERI HOLDING AS based?

HERI HOLDING AS has its business address in Oslo.

Property

Business address Gråkamveien 30, 0779 Oslo
Cadastral unit 301-41/44/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.