BIZTRAC BETA
Wholesale of other machinery and equipment

JMPI MARITIM AS

Org. no. 995065568 Limited company (AS) Kinn Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 95,000
Operating profit NOK −76,000
Equity NOK 3.0m
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76k kr).

JMPI MARITIM AS is registered as a limited company in Kinn, Vestland with organisation number 995065568. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Innkjøpstjenester for maritim virksomhet, herunder kjøp og salg/ eksport av fisk og fiskeprodukter. Investere i andre selskap med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 95,000 in revenue and NOK −76,000 in operating profit.

Key figures · 2024

Revenue
NOK 95,000
Operating profit
NOK −76,000
Equity
NOK 3.0m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns JMPI MARITIM AS?

PER IVAR SUNDSØY
JMPI MARITIM AS
NOK 95,000 rev. · NOK −76,000 profit

JMPI MARITIM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JMPI MARITIM AS

Who owns JMPI MARITIM AS?

PER IVAR SUNDSØY is the largest registered owner, with 50.0%.

What is the revenue of JMPI MARITIM AS?

JMPI MARITIM AS had revenue of NOK 95,000 in 2024.

Who is the general manager of JMPI MARITIM AS?

Per Ivar Sundsøy is registered as general manager of JMPI MARITIM AS.

Where is JMPI MARITIM AS based?

JMPI MARITIM AS has its business address in Måløy.

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.