BIZTRAC BETA
Freight transport by road

J.I. VESTLI TRANSPORT AS

Org. no. 922016267 Limited company (AS) Østre Toten Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −64,000
Equity NOK 496,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−64k kr).

J.I. VESTLI TRANSPORT AS is registered as a limited company in Østre Toten, Innlandet with organisation number 922016267. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utføre transporttjenester med lastebil, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK −64,000
Equity
NOK 496,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns J.I. VESTLI TRANSPORT AS?

JO INGE VESTLI
J.I. VESTLI TRANSPORT AS
NOK 2.7m rev. · NOK −64,000 profit

J.I. VESTLI TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J.I. VESTLI TRANSPORT AS

Who owns J.I. VESTLI TRANSPORT AS?

JO INGE VESTLI is the largest registered owner, with 100.0%.

What is the revenue of J.I. VESTLI TRANSPORT AS?

J.I. VESTLI TRANSPORT AS had revenue of NOK 2.7m in 2025.

Who is the general manager of J.I. VESTLI TRANSPORT AS?

Jo Inge Vestli is registered as general manager of J.I. VESTLI TRANSPORT AS.

Where is J.I. VESTLI TRANSPORT AS based?

J.I. VESTLI TRANSPORT AS has its business address in Kolbu.

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.