BIZTRAC BETA
Other captive investment companies

HEMA FINANS AS

Org. no. 917744556 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −168,000
Equity NOK 77.2m
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−168k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEMA FINANS AS is registered as a limited company in Stavanger, Rogaland with organisation number 917744556. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Selskapets virksomhet er å eie og investere i aksjer og andre selskaper og virksomheter, samt deltakelse av enhver art i andre forretningsforetagende og hva dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −168,000
Equity
NOK 77.2m
Est. value
NOK 76.4m

Financial health · 2024

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

Who owns HEMA FINANS AS?

M3 KRAFT AS
HEMA FINANS AS
· NOK −168,000 profit

HEMA FINANS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEMA FINANS AS own?

HEMA FINANS AS holds stakes in 21 companies:

See the full ownership structure →

Frequently asked questions about HEMA FINANS AS

Who owns HEMA FINANS AS?

M3 KRAFT AS is the largest registered owner, with 100.0%.

Who is the general manager of HEMA FINANS AS?

Henrik Heggheim is registered as general manager of HEMA FINANS AS.

Where is HEMA FINANS AS based?

HEMA FINANS AS has its business address in Stavanger.

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.