BIZTRAC BETA
Construction of residential and non-residential buildings

HM-BYGG AS

Org. no. 997385470 Limited company (AS) Sande Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −415,000
Incorporated 2011
Share capital NOK 200,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−415k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HM-BYGG AS is registered as a limited company in Sande, Møre og Romsdal with organisation number 997385470. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Bygging av bustadar og alt som er i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK −415,000

Financial health · 2025

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

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

Who owns HM-BYGG AS?

TEMA HOLDING AS
HM-BYGG AS
NOK 0 rev. · NOK −4,000 profit

HM-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HM-BYGG AS

Who owns HM-BYGG AS?

TEMA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HM-BYGG AS?

HM-BYGG AS had revenue of NOK 0 in 2025.

Where is HM-BYGG AS based?

HM-BYGG AS has its business address in Gursken.

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.