BIZTRAC BETA
Other postal and courier activities

J.L. TRANSPORT AS

Org. no. 996392015 Limited company (AS) Tønsberg Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 513,000
Equity NOK −61,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−61k kr).

J.L. TRANSPORT AS is registered as a limited company in Tønsberg, Vestfold with organisation number 996392015. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport, samt kjøp, salg og utleie i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 513,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 513,000
Equity
NOK −61,000
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-5.3%
Weak
Equity as a share of total capital

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

Who owns J.L. TRANSPORT AS?

JOSTEIN GUTTORM LIHOLM
J.L. TRANSPORT AS
NOK 2.5m rev. · NOK 513,000 profit

J.L. TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about J.L. TRANSPORT AS

Who owns J.L. TRANSPORT AS?

JOSTEIN GUTTORM LIHOLM is the largest registered owner, with 50.0%.

What is the revenue of J.L. TRANSPORT AS?

J.L. TRANSPORT AS had revenue of NOK 2.5m in 2024.

Who is the general manager of J.L. TRANSPORT AS?

Jostein Guttorm Liholm is registered as general manager of J.L. TRANSPORT AS.

Where is J.L. TRANSPORT AS based?

J.L. TRANSPORT AS has its business address in Våle.

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.