Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 05.09.2026 | Joondalup City - Armadale | 1 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 05.09.2026 | Joondalup City - Armadale | 1 - 2 | W |
| 22.08.2026 | Armadale - Perth RedStar | 0 - 4 | L |
| 15.08.2026 | Armadale - Dianella White Eagle | 3 - 1 | W |
| 01.08.2026 | Balcatta - Armadale | 3 - 3 | D |
| 25.07.2026 | Stirling Lions - Armadale | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 05.09.2026 | Joondalup City - Armadale | 1 - 2 | L |
| 22.08.2026 | Joondalup City - UWA Nedlands | 0 - 1 | L |
| 15.08.2026 | Joondalup City - Curtin University | 1 - 0 | W |
| 08.08.2026 | Inglewood United - Joondalup City | 1 - 1 | D |
| 01.08.2026 | Joondalup City - Cockburn City | 1 - 3 | L |
The upcoming match between Armadale and Joondalup City is scheduled for 12.09.2026 07:00 in Western Australia NPL. The listed venue is Alfred Skeet Reserve, Perth. 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
Armadale are in position 11 with 21 points after 20 matches. The season record is 4 wins, 6 draws and 10 losses. The goals record is 37 scored and 51 conceded. The stored form sequence is LWDDD.
Armadale recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWDDDLLWL. The averages are 1.60 goals scored and 2.70 goals conceded per match. Both teams scored in 70% of those matches, while 90% finished with over 2.5 goals. Joondalup City recorded 4 wins, 1 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLWDLLWLWW. The averages are 1.60 goals scored and 1.70 goals conceded per match. Both teams scored in 80% of those matches, while 70% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Armadale recorded 1 wins, there were 0 draws, and Joondalup City recorded 0 wins. The average total was 3 goals per match. Both teams scored in 100% of those matches, while 100% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 80%; Both teams to score — 60%; Over 0.5 first-half goals — 60%; Over 1.5 goals — 60%; Under 2.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The discipline profile for Armadale at home is based on 3 matches. The team averages 0.00 yellow cards, 1.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 100.0%. Season card data is available for 5 of 23 completed matches (21.7% coverage).
The match between Armadale and Joondalup City ended 1-1. The game produced 2 goals in total. The first half contained 1 goal. 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 BTTS at 60%. The actual outcome was BTTS. The stored trend was 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 60%. The actual outcome was Under 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 80%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 60%. The actual outcome was Over 0.5 HT. The stored trend was 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.
Of 6 verifiable pre-match indicators, 6 aligned with the final result and 0 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.