Lithuania Company Register Scraper avatar

Lithuania Company Register Scraper

Pricing

from $13.40 / 1,000 registry records

Go to Apify Store
Lithuania Company Register Scraper

Lithuania Company Register Scraper

Scrape the official Lithuanian company register (Registrų centras JAR via data.gov.lt): company code, legal name, address, registration and deregistration dates, legal form and status. One record per company. Pay per result.

Pricing

from $13.40 / 1,000 registry records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 hours ago

Last modified

Categories

Share

🔔 Lithuania Legal Entity Roster

One registry_record per Lithuanian registered legal entity (code, legal name, address, registration/deregistration dates, legal-form and status identifiers) from the official Registrų centras JAR model on get.data.gov.lt — identifiers carried verbatim, no inference.

Public, robots-honoured.

Output is one lt_legal_entity row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: get.data.gov.lt.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Lithuania Legal Entity Roster sample output — a table of real registry record rows (entity_code, legal_name, registration_date, legal_form_id) from run LskRoXCb5IgsWKnRV on build 0.1.9

Real rows from run LskRoXCb5IgsWKnRV on build 0.1.9 (2026-09-28), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

entity_codelegal_nameregistration_datelegal_form_idstatus_idstatus_date
154171066Uždarosios akcinės bendrovės "VEZO" agentūra Anykščiuose1992-06-24a13def1d-7387-4271-b206-d4a4e4e3aa035bcfd61f-7810-4946-9bd3-6de946b56f182020-12-31
254869570Individuali įmonė1997-06-038712b5b4-7934-407b-b48b-1026c87fed2f5bcfd61f-7810-4946-9bd3-6de946b56f181998-12-15
225346670Individuali įmonė2000-08-238712b5b4-7934-407b-b48b-1026c87fed2f5bcfd61f-7810-4946-9bd3-6de946b56f182002-07-10
123505646Uždaroji akcinė bendrovė "ARLANAS"1996-02-155c444113-5081-4d88-b94d-782c0779bb895bcfd61f-7810-4946-9bd3-6de946b56f182022-04-21
306462123MB Eight solutions2023-09-28cc5df44f-de10-47c4-a2b7-36191f606f265ef6b364-a5ff-47fb-8600-ff859214ef852023-09-28
120405968Individuali įmonė1991-02-188712b5b4-7934-407b-b48b-1026c87fed2f5bcfd61f-7810-4946-9bd3-6de946b56f182006-10-26
305107728Asociacija "Balta burė"2019-04-04c06e2c5e-bbc3-4654-82c7-6fd326316feb5ef6b364-a5ff-47fb-8600-ff859214ef852019-04-04
123163580Individuali įmonė1995-05-248712b5b4-7934-407b-b48b-1026c87fed2f5bcfd61f-7810-4946-9bd3-6de946b56f182022-08-11

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • record_type (string) — e.g. lt_legal_entity
  • entity_code (string/null) — e.g. 154171066
  • legal_name (string/null) — e.g. Uždarosios akcinės bendrovės "VEZO" agentūra Anykščiuose
  • full_address (string/null) — null in every sample row
  • address (string/null) — null in every sample row
  • registration_date (string/null) — e.g. 1992-06-24
  • deregistration_date (string/null) — e.g. 2020-12-31
  • legal_form_id (string/null) — e.g. a13def1d-7387-4271-b206-d4a4e4e3aa03
  • status_id (string/null) — e.g. 5bcfd61f-7810-4946-9bd3-6de946b56f18
  • status_date (string/null) — e.g. 2020-12-31
  • source (string/null) — e.g. lithuania-legal-entity-roster
  • release_date (string/null) — null in every sample row
  • source_url (string/null) — e.g. https://get.data.gov.lt/datasets/gov/rc/jar/iregistruoti/JuridinisAsmuo
  • observed_at (string/null) — e.g. 2026-09-28T06:28:42Z
  • terminal (string/integer/null) — null in every sample row
  • reported_total (string/integer/null) — null in every sample row
  • raw_seen (string/integer/null) — null in every sample row
  • duplicates (string/integer/null) — null in every sample row
  • unique_found (string/integer/null) — null in every sample row
  • delivered (string/integer/null) — null in every sample row
  • scope (string/integer/null) — null in every sample row
  • note (string/integer/null) — null in every sample row
  • license (string/integer/null) — null in every sample row
  • attribution (string/integer/null) — null in every sample row

What you get

One registry_record per record, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, reconciliation counts, and delivered/duplicate totals.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"maxRecords": 50
}

The sample run charged exactly: 4 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.08 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
"maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $100.02 on the Free tier ($0.02 start + 5000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run LskRoXCb5IgsWKnRV, exactly as it lands in the dataset (emails masked, long text shortened):

{
"record_type": "lt_legal_entity",
"entity_code": "154171066",
"legal_name": "Uždarosios akcinės bendrovės \"VEZO\" agentūra Anykščiuose",
"full_address": null,
"address": null,
"registration_date": "1992-06-24",
"deregistration_date": "2020-12-31",
"legal_form_id": "a13def1d-7387-4271-b206-d4a4e4e3aa03",
"status_id": "5bcfd61f-7810-4946-9bd3-6de946b56f18",
"status_date": "2020-12-31",
"source": "lithuania-legal-entity-roster",
"release_date": null,
"source_url": "https://get.data.gov.lt/datasets/gov/rc/jar/iregistruoti/JuridinisAsmuo",
"observed_at": "2026-09-28T06:28:42Z"
}

🔧 How it works

Transport. Requests go through Apify residential proxy because the source refuses datacenter egress. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: CRAWL_DELAY=0.15.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Entities are paged from the get.data.gov.lt Spinta model with _id-cursor pagination (limit + sort(_id) + _id> cursor), proven disjoint to an honest tail, rate-limited politely. count() reconciled. Deduped on entity code. Streaming, memory bounded.

Source

https://get.data.gov.lt/datasets/gov/rc/jar/iregistruoti/JuridinisAsmuo

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Registry Record (registry_record)$0.02$0.02$0.02$0.01

Worked at the live Free-tier price:

  • 8 registry records: $0.02 start + 8 × $0.02 = $0.18
  • 25 registry records: $0.02 start + 25 × $0.02 = $0.52
  • 5000 registry records: $0.02 start + 5000 × $0.02 = $100.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

This actor reads public, logged-out pages and feeds published by get.data.gov.lt. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (get.data.gov.lt) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers get.data.gov.lt. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source (CRAWL_DELAY=0.15) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • Residential proxy unavailable → the actor stops before touching the source and fails loud, billing nothing; make sure your plan includes residential proxy.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.