GlitchHare — stream on September 18, 2026
GlitchHare.exe now rebooting! More Overly complicated dress up sim? @maskedrukii
Started · 4h 30m · 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.
- The First Descendant10:06–14:36
View as table
| Time (UTC) | Viewers |
|---|---|
| Sep 18, 2026, 1:34 PM UTC | 86 |
| Sep 18, 2026, 1:35 PM UTC | 86 |
| Sep 18, 2026, 1:41 PM UTC | 61 |
| Sep 18, 2026, 1:47 PM UTC | 50 |
| Sep 18, 2026, 1:52 PM UTC | 51 |
| Sep 18, 2026, 1:58 PM UTC | 43 |
| Sep 18, 2026, 2:03 PM UTC | 38 |
| Sep 18, 2026, 2:08 PM UTC | 41 |
| Sep 18, 2026, 2:13 PM UTC | 35 |
| Sep 18, 2026, 2:18 PM UTC | 32 |
| Sep 18, 2026, 2:23 PM UTC | 33 |
| Sep 18, 2026, 2:28 PM UTC | 28 |
| Sep 18, 2026, 2:34 PM UTC | 30 |
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 |
|---|---|---|---|---|---|
| The First Descendant | 4h 30m | 44.0 | 86 | 198 |
How this broadcast compares
We do not yet hold enough tracked history from the last 30 days to say how this broadcast compares with a typical one for this channel.
A percentile needs at least five finalised streams in the last 90 days; we have 1.
How we measured it
- Samples collected
- 13
- Sampling coverage
- 25%
- Data confidence
- 25%
We check a live channel every few minutes rather than continuously, so these numbers are estimates built from 13 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.
Tracked since . Last updated .