LastDatabase Research

Phone Data Profile 2026

A descriptive analysis of the phone records currently stored in the LastDatabase phone dataset.

Generated: Not available

Dataset Overview

Total phone records

Estimated distinct stored phone hashes

Estimated duplicate hash records

Estimated duplicate-hash rate

0.00%

Distinct country labels

Distinct carrier labels

Distinct category labels

Field Completeness

Field completeness measures whether a database field contains a stored value. It does not independently establish accuracy, verification, deliverability, consent, or current validity.

Field	Present	Missing	Coverage

Largest Country Labels

These labels are reported as stored in the database. A stored geographic label is not automatically interpreted as a sovereign country.

Country label	Records
No country values available.

Largest Carrier Labels

Carrier	Records
No carrier values available.

Largest Category Labels

Category	Records
No category values available.

Database Timestamp Range

Earliest stored created_at: Not available

Latest stored created_at: Not available

These database timestamps describe stored database records. They should not automatically be interpreted as the date a phone number was independently verified or refreshed.

Methodology

This profile uses aggregate queries against the phone_leads dataset. Duplicate observations are based on repeated non-empty stored phone_hash values. Field-completeness percentages measure non-empty stored values.

Country, carrier, and category statistics use trimmed labels as stored in the source database. The analysis does not silently convert ambiguous labels into standardized classifications.

See the LastDatabase methodology and data-quality documentation for additional context.

Limitations

A stored phone number is not evidence that the number is currently reachable.
A stored phone hash is used for dataset-level duplicate analysis; it does not establish identity accuracy.
Field presence does not prove the correctness of the stored value.
Database timestamps do not necessarily represent an independent verification date.
Stored source or opt-in-status fields are reported as database attributes only and should not be interpreted as a blanket legal or compliance determination.