BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

HEMNES BYGG AS

Org. no. 976717260 Limited company (AS) Aurskog-Høland Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 16.3m
Operating profit NOK 160,000
Equity NOK 2.9m
Incorporated 1996
Employees 9
Share capital NOK 525,000

HEMNES BYGG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 976717260. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 1996 and has 9 registered employees. Registered share capital is NOK 525,000, divided into 525 shares. The company's stated purpose is: “Omsetning av byggevarer, og andre varer og tjenester som står i forbindelse med salg av byggevarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.3m in revenue and NOK 160,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.3m
Operating profit
NOK 160,000
Equity
NOK 2.9m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns HEMNES BYGG AS?

ARMOE HOLDING AS
HEMNES BYGG AS
NOK 16.3m rev. · NOK 160,000 profit

HEMNES BYGG AS has 2 registered shareholders:

All shareholders and roles →

Group structure

HEMNES BYGG AS er morselskap for 1 datterselskap:

Frequently asked questions about HEMNES BYGG AS

Who owns HEMNES BYGG AS?

ARMOE HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of HEMNES BYGG AS?

HEMNES BYGG AS had revenue of NOK 16.3m in 2024.

Who is the general manager of HEMNES BYGG AS?

Ole Ivar Berg is registered as general manager of HEMNES BYGG AS.

Where is HEMNES BYGG AS based?

HEMNES BYGG AS has its business address in Hemnes.

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.