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

VAADAL TRANSPORT AS

Org. no. 888410252 Limited company (AS) Kongsberg Incorporated 2005 Active
Revenue 2025 NOK 148,000
Operating profit NOK 7,000
Equity NOK 29,000
Incorporated 2005
Share capital NOK 100,000

VAADAL TRANSPORT AS is registered as a limited company in Kongsberg, Buskerud with organisation number 888410252. 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: “Godstransport på vei og alt som står i forbindelse med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 148,000 in revenue and NOK 7,000 in operating profit.

Key figures · 2025

Revenue
NOK 148,000
▼ −3 %
Operating profit
NOK 7,000
▼ −73 %
Equity
NOK 29,000
▲ +1 %
Est. value
NOK 40,000

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
10.1%
Good
Return on total assets
Solidity
39.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VAADAL TRANSPORT AS?

VAADAL TRANSPORT AS
NOK 148,000 rev. · NOK 7,000 profit

VAADAL TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VAADAL TRANSPORT AS

Who owns VAADAL TRANSPORT AS?

Helge Vaadal is the largest registered owner, with 50.0%.

What is the revenue of VAADAL TRANSPORT AS?

VAADAL TRANSPORT AS had revenue of NOK 148,000 in 2025.

Who is the general manager of VAADAL TRANSPORT AS?

Runar Vaadal is registered as general manager of VAADAL TRANSPORT AS.

Where is VAADAL TRANSPORT AS based?

VAADAL TRANSPORT AS has its business address in Kongsberg.

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.