BIZTRAC BETA
Freight transport by road

VIMME TRANSPORT AS

Org. no. 835828832 Limited company (AS) Froland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 133,000
Operating profit NOK 45,000
Equity NOK 40,000
Incorporated 2025
Share capital NOK 30,000

VIMME TRANSPORT AS is registered as a limited company in Froland, Agder with organisation number 835828832. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen lastebiltransport og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 133,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2025

Revenue
NOK 133,000
Operating profit
NOK 45,000
Equity
NOK 40,000
Est. value
NOK 152,000

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.8%
Weak
Equity as a share of total capital

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

Who owns VIMME TRANSPORT AS?

SVEIN OLAF VIMME
VIMME TRANSPORT AS
NOK 133,000 rev. · NOK 45,000 profit

VIMME TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIMME TRANSPORT AS

Who owns VIMME TRANSPORT AS?

SVEIN OLAF VIMME is the largest registered owner, with 100.0%.

What is the revenue of VIMME TRANSPORT AS?

VIMME TRANSPORT AS had revenue of NOK 133,000 in 2025.

Who is the general manager of VIMME TRANSPORT AS?

Svein Olaf Vimme is registered as general manager of VIMME TRANSPORT AS.

Where is VIMME TRANSPORT AS based?

VIMME TRANSPORT AS has its business address in Froland.

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.