Certica
Try for free

Country guide · 9 min read

Jakub Wujec

Last reviewed: 1 August 2026

How to verify a Lithuanian carrier before assigning a load

To verify a Lithuanian carrier, check public JAR for legal status, company code, address, and activity, then review financial trends, SODRA employment, and operational risk signals from enrichment data when available. Add LTSA for transport licences and CAB when you have plates for insurance. Match VIES on the PVM kodas and compare email to JAR address on booking day. An active company code in JAR does not prove a valid LTSA licence for your lane.

Key checks before you assign the load

  • Public JAR: legal status, company code, address, activity versus haulage.
  • Enrichment data: 3-year revenue, profit, equity, and liabilities trends.
  • SODRA insured employees, employment trend, and social security debt (enrichment).
  • Operational risk summary from combined enrichment signals.
  • LTSA (Vektra): transport licences and community licence flag.
  • CAB insurance with plates, plus vehicle type when CAB returns it.
  • VIES on Lithuanian VAT number.
  • Email and domain fit JAR registry data.

What to check on a Lithuanian transport company

Lithuanian carriers are keyed by company code from the Register of Legal Entities (JAR). Public JAR shows legal status, company code, address, and declared activity. Enrichment data adds 3-year financial trends, SODRA employment, and operational risk signals on top of that public status. LTSA Vektra holds licence and community licence flags. Baltic lanes often confuse Lithuanian PVM kodas validation with haulage rights.

How to check the main registers step by step

Run these on booking day and keep a screenshot or PDF in your load file.

Step 1: check the company in JAR by company code

Open Lithuanian Register of Legal Entities and search by company code, resolving it from the VAT ID (PVM kodas) if that is all you have. Public search uses an image captcha and has a daily query limit; detailed board and shareholder data need a paid Registrų centras service.

The public result shows legal form, status, registered address, and the declared activity code.

Compare the declared activity with road haulage and match the legal name against the invoice.

Step 2: check the transport licence in LTSA Vektra by company code

Open LTSA Vektra public carriers and licences. Wait for the Cloudflare security check ("Just a moment...") to finish before the public form appears, then search by company code (įmonės kodas).

Read licence validity, the community licence flag, and the assigned transport manager.

An active JAR entry with no LTSA licence record is a reason to pause before pickup details go out.

Check that the registered address matches JAR where both registers publish it.

Step 3: check VAT status in VIES by PVM kodas

Open VIES and search the PVM kodas.

VIES confirms active status and returns the registered name for that VAT ID.

Match the name against JAR and the invoice entity before payment.

What else to look for in the remaining registers

Beyond the main steps above, run these additional checks before you commit to the load.

  • Public JAR by company code resolved from VAT ID: name, legal form, status, address.
  • Enrichment data: 3-year financial trends for revenue, profit, equity, and liabilities.
  • SODRA insured employee count and monthly employment trend (enrichment).
  • SODRA social security debt, including deferred arrears (enrichment).
  • Missing revenue on an older company as a review signal.
  • Declared activity: road haulage versus forwarding, logistics, or warehousing.
  • Operational risk summary from combined enrichment signals.
  • Very new company registration as a standalone review signal.
  • LTSA: licence found, validity, community licence, transport manager assigned.
  • Plate on another operator licence copy as a subcontracting signal to clarify.
  • Registered address consistency between JAR and LTSA where both publish it.
  • VIES active status and name match to JAR and invoice.
  • CAB (plate): vehicle insurance validity on provided plates.
  • Vehicle type in CAB when returned: optional signal for commercial truck versus passenger car on a freight booking.

Lithuanian company code and PVM formats

  • Company code: 9 digits; resolved from LT VAT ID for JAR lookup.
  • PVM kodas: LT prefix plus 9 or 12 digits on invoices; VIES cross-check required.
  • LTSA shows transport manager assignment for EU operator requirements.
  • CAB insurance lookup needs Lithuanian plate format when provided.

What public JAR alone does not prove

  • LTSA licence validity or community licence for your lane.
  • CAB insurance without plates.
  • That Vektra portal PDF attached to email reflects today’s licence status.
  • Fleet size claimed in email versus LTSA licensed vehicle count.
  • Current liquidity or payment discipline from financial trends alone.
  • That SODRA employment matches the fleet size claimed in the rate email.

Example mismatch on Lithuanian lanes

Public JAR shows UAB Logistika Baltija active. Enrichment data shows flat revenue and rising liabilities over three years, with SODRA listing zero insured employees while the carrier claims twelve trucks. LTSA returns a licence but community licence flag off on a DE-LT international lane. VIES matches. Ops assumed “licence found” equals EU lane cleared. Scope and operational signals need review, not only company existence.

Documents to request from the carrier

Lithuanian carriers may send Vektra screenshots in Lithuanian without community licence column visible. Ask for LTSA line showing licence type and validity date.

  • JAR company confirmation dated to booking day.
  • LTSA licence proof for the company code.
  • VIES printout for the invoice PVM kodas.
  • Insurance documents when plates are not yet known.
  • Contract on the JAR legal name.

Email and domain checks

LT bookings sometimes use .lt domain registered recently while JAR company age is a decade. Pair domain age with LTSA transport manager name mismatch.

  • Domain age versus JAR registration timeline.
  • Website and email domain align with JAR registered address.
  • Freemail on an operator LTSA shows multiple licences needs review.
  • Verify booking contact against LTSA transport manager where listed.

Limits of a Lithuanian carrier check

Financial and SODRA enrichment can lag the booking date. Public JAR aggregated data can lag very fresh registrations. Run checks on booking day if company code resolution failed yesterday.

  • Public JAR results can be aggregated: confirm critical fields on booking day.
  • Financial and SODRA enrichment may publish with a lag versus the booking date.
  • CAB MTPL check needs plates; vehicle type is optional when CAB returns it.
  • Company code resolution from VAT ID can fail on very new entities.
  • LTSA browser registers can lag behind email rate offers.

Red flags and common mistakes

JAR active but LTSA shows no licence

May indicate a non-transport company or expired operator rights. Pause before pickup details.

Zero SODRA insured employees on a claimed fleet operator

May indicate a shell setup or undisclosed subcontracting. Requires review before high-value loads.

Company under 90 days old on a first high-value booking

Very young entities need extra register, licence, and contact checks before cargo details go out.

Rising liabilities without revenue growth over three years

Financial trend mismatch may indicate operational stress. Review against your payment terms.

SODRA social security debt above your internal threshold

Outstanding arrears can signal cash pressure. Escalate before you release pickup details.

No transport manager in LTSA for a claimed fleet operator

EU rules expect a named manager. Ask who holds responsibility before you book.

Passenger car in CAB on a goods freight booking

When CAB returns vehicle type, a passenger-car result on freight is a review signal, not a guaranteed field on every plate.

CAB shows no cover on provided plates

Insurance must be active when the truck rolls. Clear before loading.

VIES name differs from JAR legal name

Could be trading name versus legal name. Match to the invoice entity before payment.

When you do not want to repeat this for every load

Send Lithuanian VAT ID, country LT, email, and plates. Certica resolves company code, then reads public JAR status with financial and SODRA enrichment, LTSA, and CAB in parallel.

  • Public JAR status plus Certica financial trends and SODRA debt in one run.
  • Community licence flag read from LTSA, not guessed from email PDF.
  • Transport manager absence and subcontracting plate signals surfaced for review.
  • CAB validity on provided LT plates, with vehicle type when CAB returns it.

Certica

Don't want to do this on every booking?

Certica pulls data from the same registers, checks it, and shows a clear result: what is OK, and what needs clarifying before loading.

Check 20 carriers for free

Official sources

FAQ

How do I check a Lithuanian transport company?

Resolve the company code from the VAT ID and read public JAR for legal status and address on booking day. Review enrichment data for financial trends and SODRA employment. Compare with VIES, LTSA, and your contract name.

How do I assess Lithuanian carrier financial health?

Read 3-year revenue, profit, equity, and liabilities trends from enrichment data on the company register pillar. Pair trends with SODRA employment and debt signals before you approve payment terms.

What do SODRA employee counts mean in carrier verification?

SODRA enrichment shows insured employees and monthly trends. Zero employees on a claimed fleet operator is a review signal, not proof of fraud on its own.

Is an active JAR entry enough before the first load?

No. Public JAR confirms the legal entity. You still need LTSA licence scope, VIES, CAB with plates, and contact checks on booking day. Financial and SODRA signals come from enrichment, not the public JAR screen alone.

Where do I verify a Lithuanian carrier licence?

Transport licences are in the LTSA Vektra portal at LTSA Vektra public carriers and licences. Wait for the Cloudflare check to finish, then confirm licence validity, community licence, and transport manager for the company code on booking day.

What is on a Lithuanian carrier verification checklist?

Public JAR status with financial and SODRA enrichment, LTSA licence, VIES, CAB with plates, plus email and domain against JAR data.

How do I verify a Lithuanian carrier before assigning the load?

Run register, financial, LTSA, VIES, insurance, and contact checks together. One odd result is a reason to stop and review, not proof of fraud.

Related pages