BIZTRAC BETA
Freight transport by road

J.P TRANSPORT AS

Org. no. 918524487 Limited company (AS) Asker Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 18.9m
Operating profit NOK 1.2m
Equity NOK 2.3m
Incorporated 2016
Employees 10
Share capital NOK 30,000

J.P TRANSPORT AS is registered as a limited company in Asker, Akershus with organisation number 918524487. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2016 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Transport av gods på vei, samt andre produkter og tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 18.9m
Operating profit
NOK 1.2m
Equity
NOK 2.3m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns J.P TRANSPORT AS?

FRANK JOHANSEN
J.P TRANSPORT AS
NOK 18.9m rev. · NOK 1.2m profit

J.P TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J.P TRANSPORT AS

Who owns J.P TRANSPORT AS?

FRANK JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of J.P TRANSPORT AS?

J.P TRANSPORT AS had revenue of NOK 18.9m in 2024.

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

Frank Johansen is registered as general manager of J.P TRANSPORT AS.

Where is J.P TRANSPORT AS based?

J.P TRANSPORT AS has its business address in Tofte.

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.