BIZTRAC BETA
Wholesale of machine tools

KASPO MASKIN AS

Org. no. 959090750 Limited company (AS) Trondheim Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 132.0m
Operating profit NOK 2.2m
Equity NOK 8.7m
Incorporated 1990
Employees 32
Share capital NOK 2.0m

KASPO MASKIN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 959090750. The business is classified under wholesale of machine tools (NACE 46.620). The company was incorporated in 1990 and has 32 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Handel-og agenturvirksomhet samt hva hermed står i forbindelse, herunder deltakelse i andre selskaper gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 132.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 132.0m
Operating profit
NOK 2.2m
Equity
NOK 8.7m
Est. value
NOK 14.3m

Financial health · 2024

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

Who owns KASPO MASKIN AS?

M GROUP HOLDING AS
KASPO MASKIN AS
NOK 132.0m rev. · NOK 2.2m profit

KASPO MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KASPO MASKIN AS er morselskap for 1 datterselskap:

Frequently asked questions about KASPO MASKIN AS

Who owns KASPO MASKIN AS?

M GROUP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KASPO MASKIN AS?

KASPO MASKIN AS had revenue of NOK 132.0m in 2024.

Who is the general manager of KASPO MASKIN AS?

Dag Jomar Strømmen is registered as general manager of KASPO MASKIN AS.

Where is KASPO MASKIN AS based?

KASPO MASKIN AS has its business address in Trondheim.

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.