Call of Duty
Runs well
Why this badge
- Stable picture: median FPS 59, 84% of the time at 55 FPS or more.
- xCloud closed the game on the server 2 time(s) right after opening.
Summary
Ran24lasted over 10 s
Closed within 10 s28% of 26 attempts
Typical length9 minhalf of the sessions that ran lasted longer than this
Median FPS59
84% of the time at 55+
Total measured play time: 3.5 h · last version used: 0.21.44
How the sessions ended
Recorded errors
The message the app recorded when the session failed, and how many times.
Sessao xCloud falhou ServerAllocationError× 1
How long the sessions lasted
By app version
Version
Ran≤ 10 s
Median FPSTime at 55+
DropsErrors
Closed by xCloud
0.21.44
5
0
58
63%
0
0
0
0.21.43
2
0
59
90%
0
0
1
0.21.42
6
0
59
93%
0
0
0
0.21.38
1
2
59
98%
0
1
1
0.21.36
3
0
59
88%
0
0
0
0.21.35
2
0
59
65%
0
0
0
0.21.34
1
0
59
83%
0
0
0
0.21.29
2
0
59
100%
0
0
0
Latest sessions
When
VersionLength
Median FPSHow it ended
Oct 29, 2026
0.21.44
9 min
30
The player left
Oct 29, 2026
0.21.44
5 min
59
The player left
Oct 29, 2026
0.21.44
3 min
59
The player left
Oct 29, 2026
0.21.44
10 min
59
The player left
Oct 29, 2026
0.21.44
13 min
59
The player left
Oct 29, 2026
0.21.43
4 min
59
The player left
Oct 29, 2026
0.21.43
9 min
59
xCloud closed the game on the server
Oct 29, 2026
0.21.42
18 min
59
The player left
Oct 29, 2026
0.21.42
9 min
59
Free play time ran out
Oct 29, 2026
0.21.42
4 min
58
The player left
Oct 29, 2026
0.21.42
8 min
59
The player left
Oct 29, 2026
0.21.42
7 min
58
Ended normally
Tester reports about this game: 0. Issue summary in Bugs found
How we measure
The app records the frames per second every 2 s while the game runs. A session that does not pass 10 seconds counts as "opened and closed": the game did not get to run. Nothing here identifies testers or consoles.
The by-version table only shows published versions (test builds are left out). "Closed by xCloud" counts the times Microsoft's server ended the game with an error or closed it on launch.