BIZTRAC BETA
Development of building projects

HEMA EIENDOMSSELSKAP AS

Org. no. 987023635 Limited company (AS) Askøy Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 14.9m
Operating profit NOK 1.3m
Equity NOK 12.1m
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HEMA EIENDOMSSELSKAP AS is registered as a limited company in Askøy, Vestland with organisation number 987023635. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom, arbeid innen bygg og anlegg, utleie av maskiner m.v., samt det som naturlig står i denne forbindelse, og delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 14.9m
Operating profit
NOK 1.3m
Equity
NOK 12.1m
Est. value
NOK 10.6m

Financial health · 2024

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.0%
Good
Equity as a share of total capital

Who owns HEMA EIENDOMSSELSKAP AS?

FROMREIDE INVEST AS
HEMA EIENDOMSSELSKAP AS
NOK 14.9m rev. · NOK 1.3m profit

HEMA EIENDOMSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEMA EIENDOMSSELSKAP AS

Who owns HEMA EIENDOMSSELSKAP AS?

FROMREIDE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HEMA EIENDOMSSELSKAP AS?

HEMA EIENDOMSSELSKAP AS had revenue of NOK 14.9m in 2024.

Where is HEMA EIENDOMSSELSKAP AS based?

HEMA EIENDOMSSELSKAP AS has its business address in Kjerrgarden.

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.