Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 14.03.2026 | Detroit City - Brooklyn | 3 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 21.10.2026 | Brooklyn - Birmingham Legion | 1 - 2 | L |
| 17.10.2026 | Hartford Athletic - Brooklyn | 2 - 3 | W |
| 03.10.2026 | Brooklyn - Rhode Island | 1 - 3 | L |
| 30.09.2026 | Brooklyn - Detroit City | 1 - 3 | L |
| 23.09.2026 | Birmingham Legion - Brooklyn | 4 - 0 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 17.10.2026 | Tampa Bay Rowdies - Detroit City | 1 - 0 | L |
| 10.10.2026 | Detroit City - Rhode Island | 1 - 0 | W |
| 03.10.2026 | Detroit City - Birmingham Legion | 1 - 0 | W |
| 30.09.2026 | Brooklyn - Detroit City | 1 - 3 | W |
| 26.09.2026 | Detroit City - Colorado Springs | 0 - 0 | D |
The upcoming match between Brooklyn and Detroit City is scheduled for 30.09.2026 23:00 in USL Championship. The analysis uses only stored statistics, form, head-to-head records, trend percentages and active Premium market signals. It does not guarantee a particular result.
Standings and season form
Brooklyn are in position 12 with 18 points after 25 matches. The season record is 4 wins, 6 draws and 15 losses. The goals record is 25 scored and 49 conceded. The stored form sequence is LDLDL. Detroit City are in position 3 with 41 points after 25 matches. The season record is 11 wins, 8 draws and 6 losses. The goals record is 29 scored and 19 conceded. The stored form sequence is DWLDD.
Brooklyn recorded 1 wins, 2 draws and 7 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDLDLWLLLL. The averages are 0.80 goals scored and 2.30 goals conceded per match. Both teams scored in 40% of those matches, while 60% finished with over 2.5 goals. Detroit City recorded 3 wins, 5 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DWLDDWDWDL. The averages are 0.60 goals scored and 0.50 goals conceded per match. Both teams scored in 20% of those matches, while 10% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Brooklyn recorded 0 wins, there were 0 draws, and Detroit City recorded 1 wins. The average total was 3 goals per match. Both teams scored in 0% of those matches, while 100% finished with over 2.5 goals.
The highest stored values are: Under 2.5 goals — 70%; Under 3.5 goals — 70%; Over 1.5 goals — 60%; Over 0.5 first-half goals — 50%; Both teams to score — 30%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Brooklyn 0 / Detroit City 0 supports Brooklyn by an average 3.19 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 13 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. Odd/Even — Odd (odds 2).
The discipline profile for Brooklyn at home is based on 5 matches. The team averages 1.60 yellow cards, 0.60 red cards and 2.20 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 80.0%, 40.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 40.0%. Season card data is available for 15 of 25 completed matches (60.0% coverage). The discipline profile for Detroit City away from home is based on 8 matches. The team averages 2.63 yellow cards, 0.00 red cards and 2.63 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 50.0%, 12.5% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 17 of 25 completed matches (68.0% coverage).
The match between Brooklyn and Detroit City ended 1-3. The game produced 4 goals in total. The first half contained 0 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
Before kickoff, the stored trend indicated No BTTS at 70%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 60%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 70%. The actual outcome was Over 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 70%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 80%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Before kickoff, the discipline profile for Brooklyn at home was based on 5 matches, with averages of 1.6 yellow cards, 0.6 red cards and 2.2 total cards per match. In this game, Brooklyn received 0 yellow cards and 0 red cards, 0 in total. That was 2.2 cards below the stored average. In the pre-match sample, 3+ cards occurred in 40% of matches, 5+ in 0%, and a red card in 40%. Before kickoff, the discipline profile for Detroit City away from home was based on 8 matches, with averages of 2.63 yellow cards, 0 red cards and 2.63 total cards per match. In this game, Detroit City received 3 yellow cards and 0 red cards, 3 in total. That was 0.37 cards above the stored average. In the pre-match sample, 3+ cards occurred in 50% of matches, 5+ in 0%, and a red card in 0%.
The Asian-handicap signal locked before kickoff supported Brooklyn at 0. The stored market movement was 3.19 percentage points across 3 bookmakers. At the final score of 1-3, the line settled as a full loss. The Asian-handicap signal was not confirmed.
The stored Premium market was Odd at odds of 2. The actual market outcome was Even. The Premium signal was not confirmed.
Of 7 verifiable pre-match indicators, 2 aligned with the final result and 5 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.