BIZTRAC BETA
Freight transport by road

VEØY MØRE AS

Org. no. 916207808 Limited company (AS) Ålesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 189.3m
Operating profit NOK 5.6m
Equity NOK 11.2m
Incorporated 2015
Employees 124
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VEØY MØRE AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 916207808. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2015 and has 124 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Godstransport på vei samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 189.3m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 189.3m
Operating profit
NOK 5.6m
Equity
NOK 11.2m
Est. value
NOK 22.0m

Financial health · 2024

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns VEØY MØRE AS?

VEØY AS
VEØY MØRE AS
NOK 189.3m rev. · NOK 5.6m profit

VEØY MØRE AS has 3 registered shareholders:

All shareholders and roles →

Group structure

VEØY MØRE AS er morselskap for 1 datterselskap:

Frequently asked questions about VEØY MØRE AS

Who owns VEØY MØRE AS?

VEØY AS is the largest registered owner, with 51.0%.

What is the revenue of VEØY MØRE AS?

VEØY MØRE AS had revenue of NOK 189.3m in 2024.

Who is the general manager of VEØY MØRE AS?

Lars Christian Skage is registered as general manager of VEØY MØRE AS.

Where is VEØY MØRE AS based?

VEØY MØRE AS has its business address in Skodje.

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.