BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

CORRECT MASKIN AS

Org. no. 996171094 Limited company (AS) Holmestrand Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 33.5m
Operating profit NOK 1.2m
Equity NOK 7.5m
Incorporated 2010
Employees 8
Share capital NOK 100,000

CORRECT MASKIN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 996171094. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2010 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel av maskiner, produksjon og reparasjon av maskiner og utstyr, samt alt som er i tilknytning til de overnevnte punkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 33.5m
Operating profit
NOK 1.2m
Equity
NOK 7.5m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns CORRECT MASKIN AS?

ØRJAN JAHREN OLSEN
CORRECT MASKIN AS
NOK 33.5m rev. · NOK 1.2m profit

CORRECT MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CORRECT MASKIN AS

Who owns CORRECT MASKIN AS?

ØRJAN JAHREN OLSEN is the largest registered owner, with 50.0%.

What is the revenue of CORRECT MASKIN AS?

CORRECT MASKIN AS had revenue of NOK 33.5m in 2024.

Who is the general manager of CORRECT MASKIN AS?

Ørjan Jahren Olsen is registered as general manager of CORRECT MASKIN AS.

Where is CORRECT MASKIN AS based?

CORRECT MASKIN AS has its business address in Hof.

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.