biztrac. BETA
COMPANY REGISTER PROFILE
988807850 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of other machinery and equipment

MARINELEKTRONIKK AS

Org. no. 988807850 Limited company (AS) Ålesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 39.2m
Operating profit NOK 1.6m
Equity NOK 12.0m
Incorporated 2005
Employees 7
Share capital NOK 100,000

MARINELEKTRONIKK AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 988807850. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2005 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og service av skipselektronisk utstyr samt annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 39.2m
▲ +34 %
Operating profit
NOK 1.6m
▲ +7723 %
Equity
NOK 12.0m
▲ +11 %
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
2.12
Very good
Current assets ÷ current liabilities
Profitability
7.1%
Satisfactory
Return on total assets
Solidity
53.7%
Very good
Equity as a share of total capital

Who owns MARINELEKTRONIKK AS?

MARINELEKTRONIKK AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MARINELEKTRONIKK AS

Who owns MARINELEKTRONIKK AS?

Svein Arne Vatnehol is the largest registered owner, with 51.0%.

What is the revenue of MARINELEKTRONIKK AS?

MARINELEKTRONIKK AS had revenue of NOK 39.2m in 2025.

Who is the general manager of MARINELEKTRONIKK AS?

Svein Arne Vatnehol is registered as general manager of MARINELEKTRONIKK AS.

Where is MARINELEKTRONIKK AS based?

MARINELEKTRONIKK AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.