BIZTRAC BETA
Machining of metals

JS MEKANISKE VERKSTED AS

Org. no. 992643935 Limited company (AS) Nesodden Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK −171,000
Equity NOK −942,000
Incorporated 2008
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−942k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−171k kr).

JS MEKANISKE VERKSTED AS is registered as a limited company in Nesodden, Akershus with organisation number 992643935. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Drift av mekanisk verksted og contracting, samt eventuell deltagelse i tilsvarende virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK −171,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK −171,000
Equity
NOK −942,000

Financial health · 2024

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-701.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JS MEKANISKE VERKSTED AS?

CIGO AS
JS MEKANISKE VERKSTED AS
NOK 2.3m rev. · NOK −171,000 profit

JS MEKANISKE VERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JS MEKANISKE VERKSTED AS

Who owns JS MEKANISKE VERKSTED AS?

CIGO AS is the largest registered owner, with 100.0%.

What is the revenue of JS MEKANISKE VERKSTED AS?

JS MEKANISKE VERKSTED AS had revenue of NOK 2.3m in 2024.

Where is JS MEKANISKE VERKSTED AS based?

JS MEKANISKE VERKSTED AS has its business address in Fjellstrand.

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.