Families First Tournament Wrap-Up: A Huge Thank You & Congratulations to Our Champions!
The 2025 Families First Hockey Tournament has officially come to a close, and what an incredible weekend it was! From February 14 to 16, we saw intense competition, remarkable sportsmanship, and countless memories made on and off the ice.
We want to extend a heartfelt thank you to all the players, coaches, families, volunteers, and sponsors who made this event a resounding success. Your support and dedication are what make this tournament special year after year.
Congratulations to Our Champions!
After a weekend of thrilling hockey, we are excited to announce the winners of each division:
U9 Division Champions:
🏆Chatham Kent Cobra Leafs
U11 Division Champions:
🏆Amherstburg Black
U13 Division Champions:
🏆South Kent Lightning
U15 Division Champions:
🏆Port Stanley Sailors
Congratulations to all teams who competed, played hard, and showed incredible sportsmanship throughout the tournament!
Relive the Action – Order Your Tournament Photos!
Jose Castillo Photography did an outstanding job capturing all the action on the ice, the celebrations, and the unforgettable moments that made this tournament so special. If you’re looking to purchase photos from the weekend, simply scan the QR code below to visit his website and order your tournament memories today!
Thank you again to everyone who made this tournament an amazing experience. We can't wait to see you all again next year for another fantastic weekend of hockey!
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what's causing the issue — so far, it seems to appear randomly.