BIZTRAC BETA
Specialised construction activities in civil engineering

WITSØ MASKIN AS

Org. no. 979952228 Limited company (AS) Heim Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 16.9m
Operating profit NOK 1.2m
Equity NOK 1.9m
Incorporated 1998
Employees 13
Share capital NOK 100,000

WITSØ MASKIN AS is registered as a limited company in Heim, Trøndelag with organisation number 979952228. The business is classified under specialised construction activities in civil engineering (NACE 43.500). The company was incorporated in 1998 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet og alt hva som herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 16.9m
Operating profit
NOK 1.2m
Equity
NOK 1.9m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns WITSØ MASKIN AS?

MORTEN WITSØ
WITSØ MASKIN AS
NOK 16.9m rev. · NOK 1.2m profit

WITSØ MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does WITSØ MASKIN AS own?

WITSØ MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WITSØ MASKIN AS

Who owns WITSØ MASKIN AS?

MORTEN WITSØ is the largest registered owner, with 51.0%.

What is the revenue of WITSØ MASKIN AS?

WITSØ MASKIN AS had revenue of NOK 16.9m in 2024.

Who is the general manager of WITSØ MASKIN AS?

Morten Witsø is registered as general manager of WITSØ MASKIN AS.

Where is WITSØ MASKIN AS based?

WITSØ MASKIN AS has its business address in Kyrksæterøra.

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.