BIZTRAC BETA
Wholesale of machine tools

DIA PROFF NORGE AS

Org. no. 987338830 Limited company (AS) Nittedal Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 38.1m
Operating profit NOK 2.0m
Equity NOK 12.4m
Incorporated 2004
Employees 8
Share capital NOK 100,000

DIA PROFF NORGE AS is registered as a limited company in Nittedal, Akershus with organisation number 987338830. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 2004 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Engroshandel med maskiner og utstyr til bygge- og anleggsvirksomhet, import og salg av massasjestoler med tilhørende utstyr, samt annen virksomhet som måtte stå i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 38.1m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 38.1m
Operating profit
NOK 2.0m
Equity
NOK 12.4m
Est. value
NOK 11.4m

Financial health · 2024

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

Who owns DIA PROFF NORGE AS?

CRO INVEST AS
DIA PROFF NORGE AS
NOK 38.1m rev. · NOK 2.0m profit

DIA PROFF NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIA PROFF NORGE AS

Who owns DIA PROFF NORGE AS?

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

What is the revenue of DIA PROFF NORGE AS?

DIA PROFF NORGE AS had revenue of NOK 38.1m in 2024.

Who is the general manager of DIA PROFF NORGE AS?

Carl Ronny Olsen is registered as general manager of DIA PROFF NORGE AS.

Where is DIA PROFF NORGE AS based?

DIA PROFF NORGE AS has its business address in Hagan.

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.