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

HRG HOLDING AS

Org. no. 926119540 Limited company (AS) Ås Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 7.7m
Incorporated 2020
Share capital NOK 30,000

Signals

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

HRG HOLDING AS is registered as a limited company in Ås, Akershus with organisation number 926119540. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper og fast eiendom.”.

Key figures · 2025

Operating profit
NOK −8,000
▼ −10 %
Equity
NOK 7.7m
▼ −0 %
Est. value
NOK 9.1m

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 HRG HOLDING AS?

HRG HOLDING AS
· NOK −8,000 profit

HRG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HRG HOLDING AS own?

HRG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HRG HOLDING AS

Who owns HRG HOLDING AS?

HENRIK RASTEN GULLIKSEN is the largest registered owner, with 100.0%.

Where is HRG HOLDING AS based?

HRG HOLDING AS has its business address in Ås.

Property

Business address Danskerudveien 13, 1435 Ås
Cadastral unit 3218-74/36/0/0
Building Enebolig · 1 unit

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.