Season statistics
| Season | Appearances | Goals | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1st | 2nd | Unoff. | Youth | Total | 1st | 2nd | Unoff. | Youth | Total | |
| 2025–26 | 0 | 2 | 0 | 9 | 11 | 0 | 0 | 0 | 0 | 0 |
| 2026–27 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 |
| Totals | 0 | 2 | 0 | 10 | 12 | 0 | 0 | 0 | 0 | 0 |
Counted from the match line-ups and goalscorers; unused substitutes are not appearances.
Matches
12 matches and 0 goals in the archive's line-ups (all teams). Matches without a recorded line-up are not included.
- debut
- Bristol Rovers U-18s4 November 2025 · home
- last match
- Farnham Town21 July 2026 · away
Show all 12 matches
| Date | Opponent | Competition | Team | Result | Goals |
|---|---|---|---|---|---|
| 2026–27 | |||||
| 21 July 2026 | Farnham Town (a) · sub | Friendly : Academy | Youth | Lost 1–2 | |
| 2025–26 | |||||
| 11 April 2026 | Northampton Town U-18s (a) | EFL Youth Alliance League SE | Youth | Drawn 0–0 | |
| 28 March 2026 | Leyton Orient U-18s (a) | EFL Youth Alliance League SE | Youth | Lost 2–4 | |
| 24 March 2026 | Slough Town (a) | Berks & Bucks Senior Cup (2) | 2nd Team | Won 1–1 | |
| 14 February 2026 | Leyton Orient U-18s (h) | EFL Youth Alliance League SE | Youth | Drawn 2–2 | |
| 7 February 2026 | Sutton United U-18s (h) | EFL Youth Alliance League SE | Youth | Won 2–0 | |
| 31 January 2026 | Gillingham U-18s (h) | EFL Youth Alliance League SE | Youth | Won 4–1 | |
| 24 January 2026 | Stevenage U-18s (h) | EFL Youth Alliance League SE | Youth | Lost 2–3 | |
| 20 January 2026 | Bromley U-18s (a) | EFL Youth Alliance League SE | Youth | Lost 0–1 | |
| 12 November 2025 | Burnham (a) | Berks & Bucks Senior Cup (2) | 2nd Team | Won 3–0 | |
| 8 November 2025 | Oxford United U-18s (a) | EFL Youth Alliance League SE | Youth | Won 2–1 | |
| 4 November 2025 | Bristol Rovers U-18s (h) · sub | F.A. Youth Cup | Youth | Won 3–1 | |
Supporters’ memories
Memories of Archie Quinlan? Share them or a photo
Have you spotted a mistake, or got a photo or document to add? Suggest a correction
