VS
The record covers 2 completed meetings between FSV Mainz 05 and Rosenborg in 2025. FSV Mainz 05 won 1, Rosenborg won 1 and no matches ended level; the aggregate was 5–3. The fixture dated 2025-08-28 was FSV Mainz 05 4–1 Rosenborg in UEFA Europa Conference League. Another listed fixture dated 2025-08-21 was Rosenborg 2–1 FSV Mainz 05 in UEFA Europa Conference League. This summary reflects the listed completed fixtures only.
Match center
Starting eleven
Substitutes FSV Mainz 05
-
12
-
24
-
2
-
4
-
5
-
15
-
18
-
23
-
35
-
45
-
50
-
56
Rosenborg Substitutes
-
1
-
33
-
5
-
9
-
11
-
15
-
22
-
24
-
25
-
30
-
37
-
48
Match events
-
28'⚽S. Bell Normal Goal
-
34'⚽D. Islamovic Normal Goal
-
43'⚽Lee Jae-Sung Normal Goal (Asst: A. Caci)
-
44'⚽N. Weiper Normal Goal (Asst: Lee Jae-Sung)
-
46'J. Reitan-Sunde I. Fossum
-
53'Santeri Väänänen Yellow Card
-
58'⚽N. Amiri Normal Goal
-
61'E. K. Ceide O. Saeter
-
71'A. Sieb N. Weiper
-
71'S. Widmer P. Mwene
-
72'Paul Nebel Yellow Card
-
80'N. Veratschnig A. Caci
-
90'L. Maloney Lee Jae-Sung
-
90'S. Kawasaki N. Amiri
Stats for this game
Matchup FSV Mainz 05 VS Rosenborg
Record and recent results
The available record contains 2 completed meetings in 2025. FSV Mainz 05 won 1, Rosenborg won 1, and no matches ended level; the aggregate score is 5–3 in FSV Mainz 05’s favour. The fixture dated 2025-08-28 was FSV Mainz 05 4–1 Rosenborg in UEFA Europa Conference League. Another listed fixture dated 2025-08-21 was Rosenborg 2–1 FSV Mainz 05 in UEFA Europa Conference League. The balance remains a description of the listed sample.
Home context and coverage
Home results: FSV Mainz 05 won 1 of 1 matches, while Rosenborg won 1 of 1. The most represented competition is UEFA Europa Conference League with 2 recorded meetings. The record includes 0 matches decided after extra time and 0 matches decided on penalties. Home listings add context but do not establish a permanent venue-based trend. The summary uses only completed FT, AET or PEN fixtures linked to this H2H. The sample remains historical and should be read as context, not a forecast.