BIZTRAC BETA
Other specialised construction activities n.e.c.

AS DIAMANTBORING

Org. no. 927811685 Limited company (AS) Fredrikstad Incorporated 1975 Active
Ownership graph ↗
Revenue 2024 NOK 39.3m
Operating profit NOK 2.2m
Equity NOK 12.7m
Incorporated 1975
Employees 26
Share capital NOK 100,000

AS DIAMANTBORING is registered as a limited company in Fredrikstad, Østfold with organisation number 927811685. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 1975 and has 26 registered employees. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Diamantboring innenfor bygg- og anleggssektoren.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.3m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 39.3m
Operating profit
NOK 2.2m
Equity
NOK 12.7m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns AS DIAMANTBORING?

HMA HOLDING AS
AS DIAMANTBORING
NOK 39.3m rev. · NOK 2.2m profit

AS DIAMANTBORING has 4 registered shareholders:

All shareholders and roles →

Which companies does AS DIAMANTBORING own?

AS DIAMANTBORING holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about AS DIAMANTBORING

Who owns AS DIAMANTBORING?

HMA HOLDING AS is the largest registered owner, with 30.0%.

What is the revenue of AS DIAMANTBORING?

AS DIAMANTBORING had revenue of NOK 39.3m in 2024.

Who is the general manager of AS DIAMANTBORING?

Hans-Martin Andreassen is registered as general manager of AS DIAMANTBORING.

Where is AS DIAMANTBORING based?

AS DIAMANTBORING has its business address in Gressvik.

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.