Contact Us
If you have strong knowledge of the competition rules and spot something that looks wrong, please let us know — we would love to fix it.
If you would like to contact the developer, drop me a line using the contact form below.
If you have strong knowledge of the competition rules and spot something that looks wrong, please let us know — we would love to fix it.
If you would like to contact the developer, drop me a line using the contact form below.
We manage identities to ensure players with the same name do not end up on each other's profiles and to maintain accurate history.
The Challenge:
In systems like BL Rugby, different players often share the same name (e.g., multiple Finn O'Reillys). Without a unique ID, their match histories can get mixed up across different schools and clubs, leading to incorrect eligibility calculations.
The Solution:
We "cloak" (hide) unlinked or secondary identities that don't belong to the player you are currently viewing. This prevents "identity bleed" where one person's games appear on another's profile. Linking and cloaking ensures that when you look at a player, you see only their actual history, across all their teams.
Transparency:
The "Include hidden" option allows you to see any identities we've hidden for that name, so you can verify that the system has correctly separated or joined the right profiles.
This feature performs a "what-if" analysis to see if playing a match on the selected date would cause a player to become ineligible for other grades or competitions later in the season.
How it works:
Normally, the eligibility tool only checks if a player is allowed to play based on their past history. When this is enabled, it simulates the player playing the match today and then looks ahead to see if this "virtual" appearance triggers any restrictive rules that would block them from playing in their other usual teams/grades later.
Example:
If a player plays in a higher-grade Cup match today, they might be blocked from playing in a lower-grade Cup for the rest of the season. This tool will warn you about such future blocks.
Loading team sheet...
This website provides unofficial player history, match statistics, and eligibility calculations for informational and demonstration purposes only. It is an exploration of what can be achieved using Coding Agents for sports data processing.
While we strive for accuracy, data provided on this site may contain errors, be incomplete, or be outdated. This site is a mash-up of data from publicly available competition websites. Users are strictly responsible for verifying all information through official branch channels before making any sporting or eligibility decisions.
Because public rugby records do not use unique player identification numbers, multiple individuals sharing the same name may occasionally have their match histories combined. We provide identity linking and cloaking tools to mitigate this, but inaccuracies in aggregated statistics will occur. Data is provided strictly "as-is".
All competition and eligibility checks reflect automated interpretations of regulations and may not encompass special dispensation or recent committee amendments.
The search query you type into this search box checks the following fields:
Use a comma , to separate distinct search phrases (e.g. Tom Walsh, U16). Each comma-separated phrase is evaluated across any of the searchable fields:
Tom Walsh, U16 matches records that contain both "Tom Walsh" and "U16" across any searchable fields (e.g. player name and grade).The search engine automatically recognizes common Irish name variations and nicknames:
Paddy Walsh with Synonyms ON automatically finds records for Paddy Walsh, Patrick Walsh, and Pat Walsh. In Exact mode with Synonyms ON, each variant is matched as an exact term.
Synonyms Switch: When OFF, only the exact typed text is used without nickname expansion.
When the Exact switch is turned ON, search terms are strictly required to appear together within individual fields:
joe reddan requires that both "joe" and "reddan" appear in the same field (e.g. the player's name), irrespective of word order. A record where "Joe" is in one field and "Reddan" is in a different field is excluded.
, divides your search into independent field requirements. For example:
joe reddan, blackrock
You can narrow down results across multiple fields by separating terms with a comma or spaces:
Paddy Bloggs, U16
Joe Bloggs, Lansdowne
If you enclose a name or phrase in double quotation marks " ", the search engine looks for only that exact value:
"Patrick Bloggs"
Blogg will still find Bloggs).