Lithuanian Company Register Scraper
Pricing
from $2.00 / 1,000 company records
Lithuanian Company Register Scraper
[$2.00 / 1K] Bulk Lithuanian company lookup by legal entity code. Queries the JAR register, the VMI tax register, the VMI debtor list and EU VIES. Returns legal name, form, legal status, VAT registration history and the exact tax debt owed. Unmatched rows are free.
Pricing
from $2.00 / 1,000 company records
Rating
0.0
(0)
Developer
deriverge s.r.o.
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
Lithuanian Company Checker
What does Lithuanian Company Checker do?
Lithuanian Company Checker verifies Lithuanian companies in bulk against four official state sources at once. Give it a list of 9-digit legal entity codes and for each one you get back the legal name, legal form, legal status, VAT registration with its full history, an independent VIES confirmation, and the exact amount the company owes the tax authority.
The combination is the point. Each of the four sources answers a question the others cannot:
| Source | The question only it answers |
|---|---|
| JAR (Register of Legal Entities) | Is the company in liquidation, bankruptcy or restructuring? Was it deregistered, and when? |
| VMI tax register | What is its VAT number, since when, and was the registration ever cancelled? |
| VMI debtor list | How much does it owe the tax authority right now, and how much of that is past due? |
| EU VIES | Does the EU confirm the VAT number is valid for cross-border trade? |
A supplier can look perfectly alive in the tax register while the business register already lists it as Likviduojamas dėl bankroto. A name-and-address lookup will not tell you that. This actor will.
Verified zero is not a missing check
The debtor list only contains debtors, so an empty answer means verified: no tax debt, and the output says taxDebtEur: 0 rather than null. A null appears only when the check itself could not be performed, and the provenance row says why. The same honesty applies everywhere: when a source is down, the affected fields are null and flagged, never silently guessed.
Typos never reach the register
Lithuanian legal entity codes carry a checksum digit. Every code is validated locally first; a code that fails the checksum is reported as a typo, costs nothing, and never generates a request. A code that passes the checksum but does not exist is reported as such, free of charge, after checking both the register of active entities and the register of deregistered ones, because "it existed and was dissolved in 2019" is a different answer than "it never existed".
Input
{"companies": ["121215434",{ "code": "123033512", "reference": "supplier-42" }],"checkTaxDebts": true,"includeVies": true}
Strings and objects can be mixed freely. The optional reference is returned unchanged so you can join results back to your own system.
Output
One row per submitted company:
{"input": "121215434","matched": true,"code": "121215434","name": "Telia Lietuva, AB","legalForm": "Akcinė bendrovė","registeredOn": "1992-02-06","companyActive": true,"legalStatus": null,"vatNumber": "LT212154314","vatRegisteredOn": "1994-05-01","vatValidVies": true,"taxDebtEur": 0,"overdueTaxDebtEur": 0,"riskFlags": [],"provenance": [{ "source": "JAR (Registrų centras)", "ok": true },{ "source": "VMI daňový registr", "ok": true },{ "source": "VMI nedoplatky", "ok": true },{ "source": "EU VIES", "ok": true }]}
Watch a list for changes
Checking a supplier once is useful. Checking the same list every morning and reading only what changed is what keeps you out of trouble. Give the run a watch name (or save it as a task and schedule it) and every later run compares its results with the previous one: a company that turned inactive, a new risk flag, a VAT registration cancelled, a published account that disappeared. The differences are stored in the CHANGES record of the run, ready for an integration or an email. The comparison itself is free.
Pricing
| Event | Price |
|---|---|
| Run fee, a tenth of a cent per run that resolves at least one company | $0.001 |
| Company resolved | $0.004 |
| Each additional source that returned an answer | $0.001 |
| Company not found | free |
What it does not do
The register's address data sits behind a chain of separate registers and is not included yet; the address field is always null for now. If you need addresses, say so in a review and it moves up the list.
Frequently asked questions
What does an unmatched row cost? Nothing. Rows that fail the checksum or that no register knows are returned with an explanation and are never charged.
Is a zero tax debt a real answer? Yes. The debtor list contains only debtors, so an empty result is a verified zero, reported as 0. A null appears only when the check itself could not run.
Why does the answer distinguish deregistered from never existed? Because they mean different things when you vet a counterparty. A code found among deregistered entities returns the company with its removal date; a code no register knows is reported as non-existent.
Where does the data come from? The Lithuanian Register of Legal Entities and the State Tax Inspectorate (VMI), both through the national open data portal, plus EU VIES. Every value carries its source and timestamp.
Where the data comes from
All four sources are official, public and free of charge: both the Register of Legal Entities and the tax authority publish their data through the national open data portal. No scraping of web pages, no proxies, no headless browser, which keeps runs cheap and the data authoritative.
How to use Lithuanian Company Register Scraper
- Open the actor and fill in
companiesin the input form, or paste the JSON input from the example above. - Click Start. The first rows appear in the Output tab within seconds; the run summary is in the Storage tab under the key
SUMMARY. - Download the results as JSON, CSV or Excel from the Output tab, or read them through the API link shown there.
- To run it on a schedule, click Save as a task, set the input once and add a schedule. Scheduled tasks keep their own change snapshot, so the new-only mode works without any extra setup.
Integrations
The actor is available in the Apify apps for Make, Zapier, n8n and Keboola, where you pick it by name and map the input fields. It is also exposed to AI agents through the Apify MCP server, and callable from any language through the Apify API; the API tab on this page has ready-made snippets for Node.js, Python and curl. Every run can post its results to a webhook when it finishes.
Support
Questions and problems go into the Issues tab of this actor. Each issue is answered by the maintainer, and fixes ship as new builds without any change on your side.
This is the Lithuanian sibling of our Czech & Slovak and Romanian company checkers. All three share the same validation engine and the same billing rule: unmatched rows are free.