BIZTRAC BETA
Construction of bridges and tunnels

NORHARD AS

Org. no. 926060597 Limited company (AS) Sirdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 124.4m
Operating profit NOK 2.0m
Equity NOK 5.9m
Incorporated 2020
Employees 32
Share capital NOK 60,000

NORHARD AS is registered as a limited company in Sirdal, Agder with organisation number 926060597. The business is classified under construction of bridges and tunnels (NACE 42.130). The company was incorporated in 2020 and has 32 registered employees. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Utvikling, testing og markedsføring av retningsstyrt boreteknologisk utstyr spesielt tilpasset hardt fjell, samt virksomhet som står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 124.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 124.4m
Operating profit
NOK 2.0m
Equity
NOK 5.9m
Est. value
NOK 10.5m

Financial health · 2024

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

Who owns NORHARD AS?

NORHARD EQUIPMENT AS
NORHARD AS
NOK 124.4m rev. · NOK 2.0m profit

NORHARD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NORHARD AS er morselskap for 38 datterselskaper:

Frequently asked questions about NORHARD AS

Who owns NORHARD AS?

NORHARD EQUIPMENT AS is the largest registered owner, with 100.0%.

What is the revenue of NORHARD AS?

NORHARD AS had revenue of NOK 124.4m in 2024.

Who is the general manager of NORHARD AS?

Geir Birkeland is registered as general manager of NORHARD AS.

Where is NORHARD AS based?

NORHARD AS has its business address in Tonstad.

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.