BIZTRAC BETA
Freight transport by road

VEODALEN TRANSPORT AS

Org. no. 988925780 Limited company (AS) Lom Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 930,000
Equity NOK 3.3m
Incorporated 2005
Share capital NOK 100,000

VEODALEN TRANSPORT AS is registered as a limited company in Lom, Innlandet with organisation number 988925780. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport, leiekjøring og annen tilknyttet virksomhet. Selskapet kan videre drive annen virksomhet som er forenelig med de forannevnte aktivitetene, herunder å gjøre seg interessert i andre selskaper med samme eller beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 930,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 930,000
Equity
NOK 3.3m
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns VEODALEN TRANSPORT AS?

KNUT VOLE
VEODALEN TRANSPORT AS
NOK 1.9m rev. · NOK 930,000 profit

VEODALEN TRANSPORT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VEODALEN TRANSPORT AS

Who owns VEODALEN TRANSPORT AS?

KNUT VOLE is the largest registered owner, with 55.0%.

What is the revenue of VEODALEN TRANSPORT AS?

VEODALEN TRANSPORT AS had revenue of NOK 1.9m in 2025.

Who is the general manager of VEODALEN TRANSPORT AS?

Ole Vole is registered as general manager of VEODALEN TRANSPORT AS.

Where is VEODALEN TRANSPORT AS based?

VEODALEN TRANSPORT AS has its business address in Lom.

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.