Start with an explicit estimate
Kayo's table gives an example of 2.5 GB for one hour of one 720p video and 3.25 GB for one hour of one 1080p video. A simple planning calculation multiplies the per-video estimate by the number of videos and the time in hours.
The arithmetic is useful only when the assumptions remain visible. It should not be presented as a universal bitrate for every event, device or changing quality level. The phone's actual data counter and the mobile provider's billing records answer the separate question of what was used.
Worked planning examples
These are calculations using the published example rates, not recorded test results. A ninety-minute session is 1.5 hours; the example assumes the chosen quality and video count remain unchanged.
| Assumed session | Calculation | Planning estimate |
|---|---|---|
| Two 720p videos for 90 minutes | 2.5 × 2 × 1.5 | 7.5 GB |
| Two 1080p videos for 90 minutes | 3.25 × 2 × 1.5 | 9.75 GB |
| Four 720p videos for one hour | 2.5 × 4 × 1 | 10 GB |
Include the rest of the household's use
If the device is using a hotspot, other connected devices may consume the same mobile allowance. Check what is connected and distinguish the streaming session from downloads, app updates and other household traffic. A speed test does not show how much of a monthly allowance remains.
Choose a manageable number of tiles for the screen as well as the budget. Four small pictures are not automatically more useful than one main video and one secondary event. Check that the intended SplitView layout is supported on the actual device, then review the mobile account's data conditions before a long session.
Questions about this guide
Are these figures a promise of exact data usage?
No. They are worked estimates from Kayo's published table. Actual device and provider records should be used to assess real consumption.