Isaiah Leacock
Trinidadian association football player
Isaiah Israel "Bongo" Leacock (born 11 November 1999) is a Trinidadian professional footballer who plays as a forward for TT Premier Football League club San Juan Jabloteh and the Trinidad and Tobago national team.
Club career
Nicknamed Bongo, Isaiah Leacock began his career in 2022 with Harlem Strikers, scoring a hat-trick on the final matchday as the club finished third in the 2023 TT Premier Football League 2.
He then moved to AC Port of Spain in 2023 and made seven appearances for the club. He then joined Defence Force in January 2024, where he won the 2024 Trinidad and Tobago League Cup with the club, scoring a hat-trick in the final against his former club AC Port of Spain.
He then won the 2024–25 TT Premier Football League title with Defence Force and became the league's joint top scorer with fourteen goals across at least twelve matches and sixteen goals across all competitions. He had the shirt number 12 for the 2025–26 season but did not play due to injury.
Leacock joined San Juan Jabloteh on 3 January 2026, and he scored on his debut during the 3–1 loss against his former club Defence Force. He scored four goals in his first five matches for San Juan Jabloteh.
International career
Ahead of the 2025 Unity Cup, Leacock received his first call-up to the Trinidad and Tobago national team in May 2025. He debuted on 27 May 2025 during the 3–2 semi-final loss against Jamaica in which he also scored his first international goal.
This brief starts where responsible research should: with the source description of “Isaiah Leacock” as trinidadian association football player. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the people & ideas register because the source frames it as trinidadian association football player. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Chronology provides the most reliable spine for this subject; interpretation should follow only after identities and dates are secure. The source revision retrieved here is dated Aug 23, 2026. The linked authority identifier is Q134592421. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1999, 2022, 2023 and 2024.
Public reputation and documentary evidence do not always develop together; absence from a summary is not evidence of historical absence. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Read biographical claims against dates, named institutions and the cited references. Distinguish a subject’s later reputation from evidence produced during their lifetime.
- Establishing names and roles
- Building a first chronology
- Locating cited institutions
Personal papers, civil or court records, institutional files and the scholarship cited by the source.
Three-step research path
- Establish the record: confirm the title “Isaiah Leacock”, its source revision and the description used here.
- Expand the search: follow Isaiah Leacock primary sources, Isaiah Leacock archive and Isaiah research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Isaiah Leacock”?
- Which primary records establish identity, chronology and institutional ties?
- How has the subject’s reputation changed across later accounts?
Search terms from this dossier
This entry incorporates text from “Isaiah Leacock” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.