Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|
| Date | Match | Score | Res |
|---|---|---|---|
| 16.08.2026 | Caldas - Lusitano Évora 1911 | 0 - 0 | D |
| 08.08.2026 | CF Os Belenenses - Caldas | 1 - 0 | L |
| 01.08.2026 | Caldas - Academica | 2 - 2 | D |
| 02.05.2026 | 1º Dezembro - Caldas | 2 - 1 | L |
| 25.04.2026 | Caldas - SC Covilha | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Louletano - CF Os Belenenses | 1 - 3 | L |
| 08.08.2026 | Oliveirense - Louletano | 0 - 0 | D |
| 31.05.2026 | Vitória de Sernache - Louletano | 1 - 1 | D |
| 23.05.2026 | Louletano - Oliveira Hospital | 2 - 1 | W |
| 17.05.2026 | Louletano - Atlético Malveira | 1 - 1 | D |
The upcoming match between Caldas and Louletano is scheduled for 23.08.2026 16:00 in Liga 3. The listed venue is Campo da Mata, Caldas da Rainha. 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
Caldas are in position 7 with 1 points. The stored form sequence is DL. Louletano are in position 8 with 1 points. The stored form sequence is LD.
Caldas recorded 2 wins, 4 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLDLDLWDLW. The averages are 0.80 goals scored and 1.10 goals conceded per match. Both teams scored in 50% of those matches, while 30% finished with over 2.5 goals. Louletano recorded 3 wins, 4 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDDWDLDWLW. The averages are 1.50 goals scored and 1.40 goals conceded per match. Both teams scored in 90% of those matches, while 60% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 90%; Over 0.5 first-half goals — 80%; Over 1.5 goals — 70%; Under 2.5 goals — 70%; Both teams to score — 60%. They are statistical indicators and are not automatically converted into a prediction.
The discipline profile for Caldas at home is based on 1 matches. The team averages 4.00 yellow cards, 0.00 red cards and 4.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 100.0%, 100.0% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 1 of 2 completed matches (50.0% coverage).
The match between Caldas and Louletano ended 2-4. The game produced 6 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 70%. 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 90%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 80%. 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 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Before kickoff, the discipline profile for Caldas at home was based on 1 matches, with averages of 4 yellow cards, 0 red cards and 4 total cards per match. In this game, Caldas received 3 yellow cards and 0 red cards, 3 in total. That was 1 cards below the stored average. In the pre-match sample, 3+ cards occurred in 100% of matches, 5+ in 0%, and a red card in 0%.
Of 6 verifiable pre-match indicators, 4 aligned with the final result and 2 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.