Search Fixtures Players Appearances Win Ratios Data Health

Rules
School Lists
Hidden Players
Agent Findings
Support & Feedback

Exempt & Non League

Non Exempt and Non Exempt Non League Schools

Select Season

✓ 26/27 ✓ 26-27 ✓ 25-26 ✓ 24-25

Non Exempt Schools

Schools that are not exempt from standard eligibility rules.

Belvedere College

Blackrock College

CBC Monkstown

Castleknock College

Catholic University School

Cistercian College Roscrea

Clongowes Wood College

Gonzaga College

Kilkenny College

Newbridge College

Presentation College Bray

St Fintans

St. Andrews College

St. Gerard's College

St. Mary’s College

St. Michael’s College

Terenure College

The High School

The King's Hospital

Wesley College

20 Schools

Non Exempt & Non League

Non-exempt schools that also do not participate in the standard leagues.

Belvedere College

Blackrock College

Clongowes Wood College

St. Mary’s College

St. Michael’s College

Terenure College

6 Schools

Quick Navigation

Home Club Win Ratios Data Health Disclaimer Findings Contact Us Standard User Login Super Admin

Why Identity Management is Required

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.

Check for Future Blocks

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.

Player Profile & History

Team Sheet

Loading team sheet...

Confirm Action

Site Information & Disclaimer

BETA SITE Coding Agents Demonstration

Experimental Rugby Statistics Platform

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.

Data Sourcing & Accuracy Notice

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.

Player Identity & Match History

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".

Rule & Regulation Interpretations

All competition and eligibility checks reflect automated interpretations of regulations and may not encompass special dispensation or recent committee amendments.

Read Agent Findings

How Search Works

Fast, typo-tolerant search across all rugby records

Active Search Fields for This Search Box

Current Scope

The search query you type into this search box checks the following fields:

Try an Example (click any example to test):

Search Scopes (Player / Referee / Any field)

Any field (default): Searches across all available information simultaneously — player names, referee names, teams, clubs, competitions, grades, and venues.
Player: Focuses the search specifically on player profiles and club/school appearances.
Referee: Filters specifically for fixtures officiated by the named referee.

Multi-Phrase Search & Comma (,) Separators

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:

Multi-Field Matching: Entering Tom Walsh, U16 matches records that contain both "Tom Walsh" and "U16" across any searchable fields (e.g. player name and grade).
Exact Mode: Toggling Exact treats each comma-separated phrase as a strict exact term without requiring literal quotes.
Synonyms Expansion: Toggling Synonyms expands each individual phrase to include known nicknames and variations (e.g. "Tom Walsh" expands to match "Thomas Walsh" and "Tommy Walsh").

Name Variations & Nicknames (Synonyms)

Toggleable (ON / OFF)

The search engine automatically recognizes common Irish name variations and nicknames:

Patrick Paddy Pat

Searching for 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.

Exact Search & Multi-Field Matching (Exact)

Toggleable (ON / OFF)

When the Exact switch is turned ON, search terms are strictly required to appear together within individual fields:

Within-Field Match: Searching for 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.
Comma Delimited (Multi-Field Constraints): Using a comma , divides your search into independent field requirements. For example:

joe reddan, blackrock

Requires that "joe" and "reddan" both appear within one field (e.g. player name) AND "blackrock" appears in another field (e.g. club / team). Only records satisfying both constraints are returned.

Combining Search Terms with Commas or Spaces

You can narrow down results across multiple fields by separating terms with a comma or spaces:

Paddy Bloggs, U16

Finds players named Paddy / Patrick / Pat Bloggs who have played in U16 grades or competitions.

Joe Bloggs, Lansdowne

Finds player Joe Bloggs within the team or club Lansdowne.

Exact Value Matching with Double Quotes

If you enclose a name or phrase in double quotation marks " ", the search engine looks for only that exact value:

"Patrick Bloggs"

Only matches profiles that have the exact name Patrick Bloggs, skipping nickname variants like "Paddy Bloggs".

Typo Tolerance & Keyboard Shortcuts

Typo Tolerance: Small spelling errors are automatically corrected (e.g., typing Blogg will still find Bloggs).
Shortcut: Press / or Ctrl + K anywhere on the page to focus the search bar.