A Practical Audit for Gaps in a Table Tennis Rating History

To check a missing match in table tennis Elo rankings, compare the published event result with both players’ rating histories and their head-to-head record. Then rule out database update lag, duplicate identities, alternate names, active filters, ineligible match types, and a wider event-import gap. One unsuccessful name search is not enough to establish that a match is missing.

Quick checklist: confirm the gap before calling it a missing match

Use this six-step audit:

1. Record the result. Note the event, date, discipline, round, opponent, score, and result-page URL.
2. Check the database’s update date. A recent match may not have reached the rating history yet.
3. Search both player profiles. Check from each side rather than relying on one player’s displayed history.
4. Inspect the head-to-head view. Compare the date, event, round, discipline, and score.
5. Test other matches from the event. This helps distinguish one mislinked player from a broader import gap.
6. Document what you found. Save profile URLs, stable player IDs, filters used, the date checked, and related omissions.

Start with the most authoritative published result available. Depending on the competition, that may be an ITTF or WTT result, a national association record, an official league page, or the tournament organizer’s draw or results page. A social post or screenshot can help you locate the match, but the organizer’s published record is the stronger comparison source.

Record the details before searching the Elo database. Names and event labels can differ between systems, so preserving the date, round, discipline, score, opponent, and source URL gives you independent fields to compare.

This is a platform-agnostic workflow. Rating databases can have different coverage, eligibility, update, and correction rules, so an absence is not automatically an error.

Make sure you are comparing an Elo rating with the right record

Three different records are easy to confuse:

• An official or organizer-published result records the result presented for a competition.
• An independent Elo match history contains outcomes that a particular rating platform has imported and accepted for calculation.
• The ITTF world ranking awards points based on event results rather than maintaining the same kind of chronological Elo ledger.

A world-ranking points table measures event performance under its own rules. Readers who need the broader distinction can see how table tennis world rankings differ from Elo-style ratings.

These systems should not be expected to show identical records or apply identical inclusion rules.

Use the official or organizer-published result to establish the comparison record. Then consult the Elo platform’s coverage rules to determine whether that kind of match should have been imported. Do not infer eligibility merely because a match was played or published.

Audit both players, the head-to-head record, and the event

Open Player A’s history and search for Player B using whatever history, opponent, or head-to-head controls the platform provides. Compare more than the opponent’s displayed name: verify the event date, discipline, round, and score.

Repeat the process from Player B’s profile. Do not assume both profiles lead to identical underlying records.

Search for:

• Alternate spellings and spacing
• Transliteration differences
• Former or changed names
• Nationality changes
• Reversed family-name and given-name order
• Duplicate profiles
• Different stable player IDs

Also clear or expand active filters. Check date ranges, competition categories, event levels, and singles-versus-doubles views.

Where available, use head-to-head tools as another route into the record. A pseudonymous Reddit poster who identifies themselves as the rating site’s author announced player-history and head-to-head features, but that statement concerns the author’s service; it does not establish that every Elo platform offers those tools or that the service’s records are complete (author’s feature announcement).

Finally, inspect several other matches from the same tournament. If those matches appear normally, an isolated identity or record-linking problem becomes more plausible. If many matches from the same day, draw, or event are absent, classify the case as a possible event-level ingestion gap.

Hypothetical example: An official event record lists Player A against Player B in a women’s singles round of 32. The match is absent when Player A’s displayed name is searched, but a stable-ID search finds it under a duplicate Player A profile created with a different transliteration. The result was imported; the identity link, rather than the match data, caused the apparent gap.

Use a decision table to rule out common false positives

Before reporting an omission, match the pattern you see to the most likely explanation.

Observation	Likely explanation	Next check
The match is very recent	Update or processing lag	Find the latest successful update or visible refresh date, then check again after the next refresh
The match appears under only one player	Identity-linking or duplicate-profile problem	Compare stable IDs, alternate names, and both profile URLs
Many matches from one event are missing	Event-level ingestion gap	Sample other rounds, dates, and players from that event
Only doubles, qualifiers, team matches, youth matches, retirements, defaults, or walkovers are absent	Platform-specific eligibility or coverage rule	Read the platform’s exact inclusion policy for that category
The event appears in repository notes	Known or suspected data issue	Check the note’s date and compare it with the current database

Always check freshness before classifying a recent result as missing.

Do not assume every played, scheduled, or officially recorded match qualifies for Elo inclusion. If a category is consistently absent and the published policy excludes it, the absence is a coverage decision rather than a missing-match error.

If no policy is published, report the uncertainty instead of declaring the result eligible. For example: “This match does not appear in the database, and I could not find a published rule addressing team matches.”

Check coverage claims and repository notes without treating them as proof

A pseudonymous Reddit poster who identifies themselves as the rating site’s author says its loaded match history begins in 2017 and includes data accessible through WTT (author’s coverage statement). This is an attributed, unverified coverage claim—not an independent audit of completeness. “WTT-accessible data” does not establish which events, rounds, disciplines, or match statuses were actually imported. On that claimed scope, a pre-2017 match may fall outside the service’s historical coverage rather than being missing from a covered period.

Repository documentation can provide useful leads. The Chiquita repository README describes Elo ratings based on ITTF tournament data and records missing-event tasks, data-fetching problems, older API difficulties, and a possible period of manual updating. Those notes identify areas worth investigating, but they may be outdated and do not necessarily describe the current production service.

Apply a strict evidentiary boundary: a repository note naming an event can support the label “suspected import problem.” It cannot, by itself, prove that a particular match is absent from today’s database. Confirm the current player histories, event coverage, and refresh status directly.

Send a report that a maintainer can investigate

If the match remains absent after the full audit, send a concise report through the platform’s documented contact method, repository issue tracker, or correction channel. Do not guess an email address or submit the same report through unrelated channels.

Use this copy-ready template:

Subject: Suspected missing match or event-import gap

Player A:
Stable player ID:
Player A profile URL:

Player B:
Stable player ID:
Player B profile URL:

Event:
Date:
Discipline:
Round:
Score:
Official or organizer result URL:

Database date checked:
Database update or refresh date, if shown:
Filters and date ranges checked:
Alternate names or IDs checked:
Head-to-head result:
Related missing matches from the same event:

Status:
I checked both profiles, alternate names or IDs, the head-to-head view,
relevant filters, and other matches from the event.

Assessment:
[Suspected isolated missing match / suspected identity-linking issue /
suspected event-level import gap / eligibility unclear]

Describe uncertainty accurately. If several matches from one tournament are absent, report a “suspected event-level import gap” rather than asserting that the database is broken. If the result appears under a duplicate profile, identify both records and request a review of the player linkage.

A match should be called missing only after both player identities, the head-to-head record, database freshness, filters, eligibility rules, and event-wide coverage have been checked against an authoritative published result. If the gap remains, a precise, source-backed report gives the maintainer the best chance of diagnosing and correcting it.