BIZTRAC BETA
Repair and maintenance of civilian ships and boats

YMEK AS

Org. no. 966918675 Limited company (AS) Lødingen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 25.3m
Operating profit NOK −4.3m
Equity NOK 9.5m
Incorporated 1993
Employees 26
Share capital NOK 1.6m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,3 mill kr).

YMEK AS is registered as a limited company in Lødingen, Nordland with organisation number 966918675. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 1993 and has 26 registered employees. Registered share capital is NOK 1.6m, divided into 1600 shares. The company's stated purpose is: “Å drive med leveranser av varer og tjenester til skip/båter, samt til bygge- og anleggsvirksomhet på land. ”. The most recent filed accounts, for the 2024 financial year, show NOK 25.3m in revenue and NOK −4.3m in operating profit.

Key figures · 2024

Revenue
NOK 25.3m
Operating profit
NOK −4.3m
Equity
NOK 9.5m
Est. value
NOK 7.3m

Financial health · 2024

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

Who owns YMEK AS?

YTTERSTAD FISKERISELSKAP AS
YMEK AS
NOK 25.3m rev. · NOK −4.3m profit

YMEK AS has 1 registered shareholder:

All shareholders and roles →

Group structure

YMEK AS er morselskap for 9 datterselskaper:

Frequently asked questions about YMEK AS

Who owns YMEK AS?

YTTERSTAD FISKERISELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of YMEK AS?

YMEK AS had revenue of NOK 25.3m in 2024.

Who is the general manager of YMEK AS?

Ole Anders Strand is registered as general manager of YMEK AS.

Where is YMEK AS based?

YMEK AS has its business address in Lødingen.

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.