Venezuela Te Busca β€” reunir familiasVenezuela Te Busca β€” reuniting families

Tilores provides no information about missing people.

We are a technology company: we help organise and clean up records. We do not provide information about any individual, and the data we processed is not an official source and is not fully accurate. If you are looking for a loved one or want to report a case, please go directly to the official registries:

One registry,
one record per person

After the La Guaira earthquake, venezuelareporta.org maintains a public registry β€” with an open API β€” where anyone can report a missing relative. The same person is often reported many times. Tilores consolidates every report into one record per real person β€” without losing a single contact β€” and leaves every decision in human hands.

We take the data from venezuelareporta.org's public API; the same registry also appears on venezuelatebusca.com. We run it all through Tilores entity resolution and publish the results free to organisations and families searching in Venezuela.


Results

The registry's figures, deduplicated

Last updated: 29 June 2026, 06:07 VET (12:07 CEST) Β· incremental import

53,693
Reports received

Resolved into 51,622 distinct people

2,071
Duplicate reports merged

Across 1,579 people with more than one report

273
Urgent cases

"Missing" but already has a "found / safe" record

51,622
Distinct people

One consolidated record per person

6,132
people found or safe
45,490
still missing

Each report's identifier is the project's own database UUID, so the results map back one-to-one and can be applied directly.


Running the search? We can keep the deduplication current.

These figures were updated on 29-06-2026 with an incremental import: only new or changed reports are re-processed. Send us the raw data and we'll keep the results current against the latest version of the registry. Write to us at hello@tilores.io.


Hospital screening

Hospital patients, cross-referenced with the missing-persons registry

Screened on 29 June 2026, 09:33 VET (15:33 CEST)

buscatupaciente.com β†—, a hospital-patient platform, asked us to cross-reference their patient list against the public missing-persons registry (venezuelareporta.org): to find people reported missing who may in fact be patients in a hospital. We screened about 9,053 patients with Tilores entity resolution β€” each patient searched by national ID (cΓ©dula) and name, with a name- and age-agreement check β€” and tiered every match by confidence.

9,053
Patients screened

2,696 had enough data; 6,357 with no cΓ©dula or full name were excluded to avoid false positives

751
Candidate matches

All for human review β€” none confirmed automatically

414
Near-certain

Both national ID and name agree

61
Priority: reunification

High/medium confidence, still marked missing, and the name does not contradict

520
HIGH Β· exact national ID
49
MEDIUM Β· name + age
147
LOW Β· name only
35
FLAG Β· conflicting ID

Most matches were already marked found or safe in the registry β€” confirmation, not news. That's why the actionable subset is the 61 people still marked missing: possible live reunifications.

How to read this. The only signals available were national ID, name, and age (the patient data had no usable gender or location). A national-ID match is strong but not infallible: a name-agreement check flagged 72 ID matches whose names disagree (probably mistyped IDs). Every match is for human review; nothing is auto-confirmed or auto-closed, because a wrong match could stop the search for someone still missing. Results are a snapshot and refresh as the underlying data changes.


The challenge

In a crisis, duplicate reports cost time

When many people report at once, duplicates are not a cosmetic problem. They inflate the apparent number of missing people, scatter one person's information across several reports, and bury the fact that matters most: that someone has already been found.

Someone comparing two lists by hand cannot reliably tell that "MarΓ­a C. GonzΓ‘lez" and "Maria Gonzalez" are the same person, or that a missing report already has a "found" report waiting elsewhere in the data.


What Tilores did

Entity resolution, in plain language

Entity resolution is the technology that recognises when several records refer to the same real person, even when the details are written differently. We ingested the full registry and resolved it into distinct people. Matching is anchored on the national ID (cΓ©dula), plus name, age, and last-seen location.

Safeguards against false matches

On a subject this sensitive, a false positive is worse than no match. So the configuration is deliberately cautious:

Siblings are not merged
The first given name must match, so different relatives aren't merged together.
Reports mixing several people
Reports that mix several people ("X y Y") are excluded from automatic merging.
Fast and repeatable

About 53,500 records were submitted in roughly 60 seconds. Entity resolution runs on the instance and refreshes incrementally: each update re-processes only new or changed reports.


How the data is used responsibly

Humans stay in control

Every match is a suggestion for human review. A person confirms before any case is closed, because a wrong match could stop the search for someone still missing.

We are also honest about the limits of this data: on this occasion the public API withheld reporter phone and email, so matching relied on weaker signals β€” a cΓ©dula is present in only about 18% of reports, alongside name, age, and location. Real duplicates are likely undercounted; richer data would catch more.

This version is based on data obtained from the public API of venezuelareporta.org (updated 29-06-2026), which holds the same registry of reports. The results are a snapshot of that moment and an aid to human review, not a definitive identification.

We are not yet in direct contact with venezuelareporta.org. We'd welcome the chance to talk with their team and help directly. If you're part of the project β€” or can connect us β€” write to us at hello@tilores.io.


What we delivered

Three deliverables, ready to use

A golden record per person

One record per real person: merged fields from all their reports, every reporter’s contact details, and a "found / safe" status if any of their reports indicated one.

Duplicate clusters

Which reports to merge for each person, keeping one primary, using the original database UUIDs.

Priority "missing-but-found" list

The most urgent output: 273 cases where matching a missing report to a "found / safe" report can close a case.


What's next Β· How Tilores can help

Prevent duplicates at the source and screen hospital lists

Real-time deduplication via API

Dedupe and search the moment each new report is captured, preventing duplicates at the source instead of cleaning them up afterwards.

Automatic hospital-list screening

Compare lists of admitted or identified patients against the registry to surface likely matches and help reunite people with their families faster.

We've now screened a first hospital list

On 29-06-2026 we screened ~9,053 patients from buscatupaciente.com against the missing-persons registry (see "Hospital screening" above). The screening can run continuously via API as new patient lists and reports arrive.


Would this help? Let's talk.

If you run a registry, a relief effort, or a hospital's data, we'd be glad to talk. Tilores offers this free to those searching in Venezuela.