BIZTRAC BETA
Other building completion and finishing

MØRE PORTSERVICE AS

Org. no. 918146288 Limited company (AS) Volda Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK −141,000
Equity NOK 996,000
Incorporated 2016
Share capital NOK 60,000

Signals

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

MØRE PORTSERVICE AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 918146288. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2016. Registered share capital is NOK 60,000, divided into 200 shares. The company's stated purpose is: “Service, reparasjoner og montering av porter, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK −141,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK −141,000
Equity
NOK 996,000
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns MØRE PORTSERVICE AS?

TOMMY LØVIK
MØRE PORTSERVICE AS
NOK 9.4m rev. · NOK −141,000 profit

MØRE PORTSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MØRE PORTSERVICE AS

Who owns MØRE PORTSERVICE AS?

TOMMY LØVIK is the largest registered owner, with 50.0%.

What is the revenue of MØRE PORTSERVICE AS?

MØRE PORTSERVICE AS had revenue of NOK 9.4m in 2025.

Who is the general manager of MØRE PORTSERVICE AS?

Geir Storeide is registered as general manager of MØRE PORTSERVICE AS.

Where is MØRE PORTSERVICE AS based?

MØRE PORTSERVICE AS has its business address in Volda.

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.