BIZTRAC BETA
COMPANY REGISTER PROFILE
835044262 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Freight transport by road

LONGTRADERS AS

Org. no. 835044262 Limited company (AS) Tønsberg Incorporated 1984 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK 598,000
Incorporated 1984
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LONGTRADERS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 835044262. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1984. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Transportvirksomhet, spedisjon, agenturvirksomhet, deltakelse i andre selskaper og alt som hermed står i forbindelse.”.

Former names: TØNSBERG VAREDISTRIBUNAL AS

Key figures · 2025

Operating profit
NOK −25,000
▼ −43 %
Equity
NOK 598,000
▲ +0 %
Est. value
NOK 635,000

Financial health · 2025

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

Who owns LONGTRADERS AS?

LONGTRADERS AS
· NOK −25,000 profit

LONGTRADERS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LONGTRADERS AS er morselskap for 2 datterselskaper:

Frequently asked questions about LONGTRADERS AS

Who owns LONGTRADERS AS?

FJORDGATEN INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of LONGTRADERS AS?

Johan Ansgar Asplin is registered as general manager of LONGTRADERS AS.

Where is LONGTRADERS AS based?

LONGTRADERS AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.