BIZTRAC BETA
Site preparation

JENSTAD MASKIN AS

Org. no. 912182304 Limited company (AS) Sunndal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 29.6m
Operating profit NOK −471,000
Equity NOK 1.5m
Incorporated 2013
Employees 15
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−471k kr).

JENSTAD MASKIN AS is registered as a limited company in Sunndal, Møre og Romsdal with organisation number 912182304. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.6m in revenue and NOK −471,000 in operating profit.

Key figures · 2025

Revenue
NOK 29.6m
Operating profit
NOK −471,000
Equity
NOK 1.5m
Est. value
NOK 10.9m

Financial health · 2025

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

Who owns JENSTAD MASKIN AS?

EIVIND JENSTAD
JENSTAD MASKIN AS
NOK 29.6m rev. · NOK −471,000 profit

JENSTAD MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JENSTAD MASKIN AS own?

JENSTAD MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JENSTAD MASKIN AS

Who owns JENSTAD MASKIN AS?

EIVIND JENSTAD is the largest registered owner, with 100.0%.

What is the revenue of JENSTAD MASKIN AS?

JENSTAD MASKIN AS had revenue of NOK 29.6m in 2025.

Who is the general manager of JENSTAD MASKIN AS?

Eivind Jenstad is registered as general manager of JENSTAD MASKIN AS.

Where is JENSTAD MASKIN AS based?

JENSTAD MASKIN AS has its business address in Gjø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.