BIZTRAC BETA
Freight transport by road

JLS TRANSPORT AS

Org. no. 998012880 Limited company (AS) Larvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK −282,000
Equity NOK 2.3m
Incorporated 2012
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−282k kr).

JLS TRANSPORT AS is registered as a limited company in Larvik, Vestfold with organisation number 998012880. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 5000 shares. The company's stated purpose is: “Landbasert transport på vei og bane, generell befraktning og annet som herved står i forbindelse. Investeringer i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK −282,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK −282,000
Equity
NOK 2.3m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns JLS TRANSPORT AS?

JACEK SZYSZLO
JLS TRANSPORT AS
NOK 8.7m rev. · NOK −282,000 profit

JLS TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JLS TRANSPORT AS

Who owns JLS TRANSPORT AS?

JACEK SZYSZLO is the largest registered owner, with 50.0%.

What is the revenue of JLS TRANSPORT AS?

JLS TRANSPORT AS had revenue of NOK 8.7m in 2024.

Who is the general manager of JLS TRANSPORT AS?

Jacek Szyszlo is registered as general manager of JLS TRANSPORT AS.

Where is JLS TRANSPORT AS based?

JLS TRANSPORT AS has its business address in Larvik.

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.