betitoDeidadSyGOD — stream on September 16, 2026
Drops Pokemon Badges Betito !danger !drop !webs !pokemon !pin !commands
Started · 22h 9m · ended
Estimated
Viewers during this broadcast
Sampled every few minutes. Breaks in the line are stretches we did not observe — they are never drawn across.
- Pokémon GO21:54–20:04
View as table
| Time (UTC) | Viewers |
|---|---|
| Sep 16, 2026, 9:58 PM UTC | 20 |
| Sep 16, 2026, 10:13 PM UTC | 27 |
| Sep 16, 2026, 10:27 PM UTC | 26 |
| Sep 16, 2026, 10:41 PM UTC | 40 |
| Sep 16, 2026, 10:54 PM UTC | 41 |
| Sep 16, 2026, 11:08 PM UTC | 35 |
| Sep 16, 2026, 11:24 PM UTC | 31 |
| Sep 16, 2026, 11:37 PM UTC | 42 |
| Sep 16, 2026, 11:52 PM UTC | 29 |
| Sep 17, 2026, 12:06 AM UTC | 27 |
| Sep 17, 2026, 12:21 AM UTC | 26 |
| Sep 17, 2026, 12:36 AM UTC | 30 |
| Sep 17, 2026, 12:49 AM UTC | 42 |
| Sep 17, 2026, 1:04 AM UTC | 28 |
| Sep 17, 2026, 1:17 AM UTC | 27 |
| Sep 17, 2026, 1:32 AM UTC | 24 |
| Sep 17, 2026, 1:46 AM UTC | 37 |
| Sep 17, 2026, 2:02 AM UTC | 34 |
| Sep 17, 2026, 2:15 AM UTC | 38 |
| Sep 17, 2026, 2:30 AM UTC | 27 |
| Sep 17, 2026, 2:43 AM UTC | 31 |
| Sep 17, 2026, 2:57 AM UTC | 40 |
| Sep 17, 2026, 3:11 AM UTC | 42 |
| Sep 17, 2026, 3:24 AM UTC | 33 |
| Sep 17, 2026, 3:39 AM UTC | 35 |
| Sep 17, 2026, 3:54 AM UTC | 23 |
| Sep 17, 2026, 4:08 AM UTC | 32 |
| Sep 17, 2026, 4:21 AM UTC | 19 |
| Sep 17, 2026, 4:37 AM UTC | 21 |
| Sep 17, 2026, 4:52 AM UTC | 20 |
| Sep 17, 2026, 5:07 AM UTC | 33 |
| Sep 17, 2026, 5:21 AM UTC | 28 |
| Sep 17, 2026, 5:34 AM UTC | 24 |
| Sep 17, 2026, 5:47 AM UTC | 35 |
| Sep 17, 2026, 6:01 AM UTC | 37 |
| Sep 17, 2026, 6:14 AM UTC | 25 |
| Sep 17, 2026, 6:27 AM UTC | 34 |
| Sep 17, 2026, 6:41 AM UTC | 38 |
| Sep 17, 2026, 6:56 AM UTC | 36 |
| Sep 17, 2026, 7:12 AM UTC | 34 |
| Sep 17, 2026, 7:25 AM UTC | 25 |
| Sep 17, 2026, 7:39 AM UTC | 24 |
| Sep 17, 2026, 7:52 AM UTC | 30 |
| Sep 17, 2026, 8:07 AM UTC | 36 |
| Sep 17, 2026, 8:20 AM UTC | 29 |
| Sep 17, 2026, 8:32 AM UTC | 28 |
| Sep 17, 2026, 8:45 AM UTC | 19 |
| Sep 17, 2026, 8:59 AM UTC | 27 |
| Sep 17, 2026, 9:12 AM UTC | 33 |
| Sep 17, 2026, 9:27 AM UTC | 31 |
| Sep 17, 2026, 9:41 AM UTC | 22 |
| Sep 17, 2026, 9:55 AM UTC | 25 |
| Sep 17, 2026, 10:10 AM UTC | 23 |
| Sep 17, 2026, 10:23 AM UTC | 36 |
| Sep 17, 2026, 10:38 AM UTC | 25 |
| Sep 17, 2026, 10:54 AM UTC | 26 |
| Sep 17, 2026, 11:08 AM UTC | 23 |
| Sep 17, 2026, 11:23 AM UTC | 24 |
| Sep 17, 2026, 11:38 AM UTC | 35 |
| Sep 17, 2026, 11:52 AM UTC | 33 |
| Sep 17, 2026, 12:08 PM UTC | 34 |
| Sep 17, 2026, 12:23 PM UTC | 37 |
| Sep 17, 2026, 12:37 PM UTC | 33 |
| Sep 17, 2026, 12:52 PM UTC | 24 |
| Sep 17, 2026, 1:05 PM UTC | 35 |
| Sep 17, 2026, 1:18 PM UTC | 25 |
| Sep 17, 2026, 1:32 PM UTC | 32 |
| Sep 17, 2026, 1:45 PM UTC | 44 |
| Sep 17, 2026, 1:59 PM UTC | 44 |
| Sep 17, 2026, 2:14 PM UTC | 43 |
| Sep 17, 2026, 2:28 PM UTC | 33 |
| Sep 17, 2026, 2:42 PM UTC | 28 |
| Sep 17, 2026, 2:56 PM UTC | 43 |
| Sep 17, 2026, 3:09 PM UTC | 33 |
| Sep 17, 2026, 3:25 PM UTC | 40 |
| Sep 17, 2026, 3:39 PM UTC | 40 |
| Sep 17, 2026, 3:54 PM UTC | 46 |
| Sep 17, 2026, 4:09 PM UTC | 43 |
| Sep 17, 2026, 4:22 PM UTC | 36 |
| Sep 17, 2026, 4:36 PM UTC | 44 |
| Sep 17, 2026, 4:50 PM UTC | 41 |
| Sep 17, 2026, 5:06 PM UTC | 50 |
| Sep 17, 2026, 5:21 PM UTC | 46 |
| Sep 17, 2026, 5:34 PM UTC | 40 |
| Sep 17, 2026, 5:48 PM UTC | 43 |
| Sep 17, 2026, 6:04 PM UTC | 53 |
| Sep 17, 2026, 6:18 PM UTC | 55 |
| Sep 17, 2026, 6:34 PM UTC | 52 |
| Sep 17, 2026, 6:48 PM UTC | 52 |
| Sep 17, 2026, 7:02 PM UTC | 49 |
| Sep 17, 2026, 7:18 PM UTC | 48 |
| Sep 17, 2026, 7:30 PM UTC | 56 |
| Sep 17, 2026, 7:42 PM UTC | 46 |
| Sep 17, 2026, 7:55 PM UTC | 34 |
| Sep 17, 2026, 8:02 PM UTC | 47 |
Category timeline
Where the broadcast’s time went. A switch is placed midway between the last sample of one category and the first of the next, because that is as precisely as sampling can locate it.
| Category | Started (UTC) | Duration | Avg viewers | Peak | Hours watched |
|---|---|---|---|---|---|
| Pokémon GO | 22h 9m | 34.2 | 58 | 759 |
How this broadcast compares
This broadcast averaged 34.2 viewers, 83.3% below the channel’s 30-day average of 205 viewers.
This broadcast drew a higher average audience than 6% of the 17 streams we finalised for this channel in the last 90 days.
How we measured it
- Samples collected
- 375
- Sampling coverage
- 100%
- Data confidence
- 100%
We check a live channel every few minutes rather than continuously, so these numbers are estimates built from 375 observations. Coverage is the share of the broadcast those observations account for; confidence combines that coverage with how many samples we took and whether we saw the stream end. Time we did not observe is excluded from the averages rather than filled in.
What stands out
- This stream averaged −83.3% versus the channel's 30-day average of 205 viewers.
Tracked since . Last updated .