Announcing the first ever tournament of players who make players, SWYNG Badminton Coaches Cup on Thursday 19 December 2019, at Sarjapur-Bellandur
- Last date to register is 17th Dec 2019
Categories
Singles (Gender Neutral)
Participation Fee & Details
Entry Fee: Rs. 400/-
- Maximum participation: 64 players
- No limits on player's district, state, national or international credentials.
- However, all players must present a substantial proof that they coach Badminton. It can be ID card/note from an academy or their trainees/ trainee's kin. Please mention the academy name in the registration form. Please mention 'Independent Coach' if you are an independent coach and not attached to any academy.
Prizes
- Trophy for the champion and medals for top 3 finishers.
- Sports goodies for the champion (Kit bag, a racquet, shuttle barrel, pair of shoes and T shirt) and the runner up (Kit bag and T-shirt). T-shirt for 3rd and 4th position.
Format
Knockout. All matches are played for best of three 21 point set.
Additional Info
- Event starts from 5 PM onwards (tentatively)
- Standard Badminton rules are followed.
- Yonex Mavis 350 or equivalent feather shuttles will be used.
- Last date to register is 17 Dec 2019
- Fixtures & Schedule will be shared at least a day prior to the tournament day.
- It becomes extremely difficult to entertain individual requests for changes in the fixtures and matches schedule. So, let's avoid that. Fixture & schedule once published cannot be changed.
- SWYNG deserves the right to modify the dates/format for reasons beyond their control and will be duly communicated.
- SWYNG also deserves the right to modify/scrap a category/prize money depending on the participation count.
- Referees and the organizers decision will be binding.
- All participants are responsible for their personal safety and by registering agree to the standard terms & conditions of any tournament.
Date & Time
19th December 2019
9 PM onwards
Location
SWYNG Badminton Whitefield - Gopalan National School
Buy Tickets
Categories
Apologies, there seems to be a configuration issue with the event. We're working on resolving it. Thank you for your understanding.