Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 19.04.2026 | TB - Víkingur II | 2 : 0 |
| 17.08.2024 | Víkingur II - TB | 1 : 1 |
| 03.07.2024 | TB - Víkingur II | 0 : 1 |
| 10.03.2024 | TB - Víkingur II | 2 : 3 |
| 01.10.2022 | Víkingur II - TB | 4 : 2 |
| 13.08.2022 | TB - Víkingur II | 3 : 4 |
| 23.04.2022 | Víkingur II - TB | 1 : 2 |
| 16.08.2014 | TB - Víkingur II | 0 : 1 |
| 21.06.2014 | Víkingur II - TB | 0 : 7 |
| 19.04.2014 | TB - Víkingur II | 1 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 29.08.2026 | TB - NSÍ II | 5 - 1 | W |
| 22.08.2026 | EB / Streymur II - TB | 2 - 2 | D |
| 15.08.2026 | B36 II - TB | 3 - 4 | W |
| 08.08.2026 | TB - ÍF II | 0 - 3 | L |
| 01.08.2026 | HB II - TB | 1 - 3 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 29.08.2026 | Víkingur II - HB II | 2 - 0 | W |
| 22.08.2026 | B71 - Víkingur II | 3 - 0 | L |
| 15.08.2026 | Víkingur II - ÍF II | 4 - 1 | W |
| 08.08.2026 | NSÍ II - Víkingur II | 1 - 4 | W |
| 01.08.2026 | Víkingur II - Hoyvík | 2 - 0 | W |
The upcoming match between TB and Víkingur II is scheduled for 07.09.2026 15:00 in 1. Deild. 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
TB are in position 5 with 26 points after 17 matches. The season record is 6 wins, 4 draws and 7 losses. The goals record is 29 scored and 35 conceded. The stored form sequence is DWLWW. Víkingur II are in position 2 with 45 points after 17 matches. The season record is 12 wins, 3 draws and 2 losses. The goals record is 44 scored and 25 conceded. The stored form sequence is LWWWW.
TB recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWLWWLLDL. The averages are 2.20 goals scored and 2.30 goals conceded per match. Both teams scored in 90% of those matches, while 100% finished with over 2.5 goals. Víkingur II recorded 8 wins, 0 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWWWWWWLW. The averages are 2.80 goals scored and 1.70 goals conceded per match. Both teams scored in 60% of those matches, while 80% finished with over 2.5 goals.
Across the last 10 head-to-head matches, TB recorded 4 wins, there were 1 draws, and Víkingur II recorded 5 wins. The average total was 3.50 goals per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 100%; Over 2.5 goals — 80%; Over 0.5 first-half goals — 70%; Both teams to score — 60%; Over 3.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The match between TB and Víkingur II ended 2-3. The game produced 5 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.
The previous 10 head-to-head meetings averaged 3.5 goals, while this match produced 5. The final scoring profile differed by more than one goal from that average.
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 100%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 2.5 at 80%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 3.5 at 60%. The actual outcome was Over 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 70%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result.
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.