biztrac. BETA
COMPANY REGISTER PROFILE
936218059 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

VAADAN TRANSPORT AS

Org. no. 936218059 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 90.1m
Operating profit NOK 8.7m
Equity NOK 19.0m
Incorporated 2025
Employees 79
Share capital NOK 131,000

VAADAN TRANSPORT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 936218059. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025 and has 79 registered employees. Registered share capital is NOK 131,000, divided into 2616 shares. The company's stated purpose is: “Transportvirksomhet og alt som naturlig knyttet seg til dette, samt deltakelse i andre selskap med kapital.”. The most recent filed accounts, for the 2025 financial year, show NOK 90.1m in revenue and NOK 8.7m in operating profit.

Key figures · 2025

Revenue
NOK 90.1m
Operating profit
NOK 8.7m
Equity
NOK 19.0m
Est. value
NOK 39.0m

Financial health · 2025

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

Who owns VAADAN TRANSPORT AS?

VAADAN TRANSPORT AS
NOK 90.1m rev. · NOK 8.7m profit

VAADAN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VAADAN TRANSPORT AS

Who owns VAADAN TRANSPORT AS?

ATVA AS is the largest registered owner, with 100.0%.

What is the revenue of VAADAN TRANSPORT AS?

VAADAN TRANSPORT AS had revenue of NOK 90.1m in 2025.

Who is the general manager of VAADAN TRANSPORT AS?

Atle Vaadan is registered as general manager of VAADAN TRANSPORT AS.

Where is VAADAN TRANSPORT AS based?

VAADAN TRANSPORT AS has its business address in Tiller.

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.