MehMasha — stream on September 2, 2026
Тестируем локальные модели, экономим деньги!
Started · 6h 56m · 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.
- Software and Game Development16:01–22:58
View as table
| Time (UTC) | Viewers |
|---|---|
| Sep 2, 2026, 4:19 PM UTC | 152 |
| Sep 2, 2026, 4:23 PM UTC | 154 |
| Sep 2, 2026, 4:27 PM UTC | 164 |
| Sep 2, 2026, 4:31 PM UTC | 205 |
| Sep 2, 2026, 4:38 PM UTC | 208 |
| Sep 2, 2026, 4:41 PM UTC | 204 |
| Sep 2, 2026, 4:45 PM UTC | 220 |
| Sep 2, 2026, 4:49 PM UTC | 229 |
| Sep 2, 2026, 4:54 PM UTC | 218 |
| Sep 2, 2026, 4:57 PM UTC | 218 |
| Sep 2, 2026, 5:00 PM UTC | 209 |
| Sep 2, 2026, 5:04 PM UTC | 207 |
| Sep 2, 2026, 5:09 PM UTC | 203 |
| Sep 2, 2026, 5:14 PM UTC | 226 |
| Sep 2, 2026, 5:18 PM UTC | 242 |
| Sep 2, 2026, 5:22 PM UTC | 218 |
| Sep 2, 2026, 5:25 PM UTC | 238 |
| Sep 2, 2026, 5:29 PM UTC | 233 |
| Sep 2, 2026, 5:34 PM UTC | 217 |
| Sep 2, 2026, 5:39 PM UTC | 233 |
| Sep 2, 2026, 5:43 PM UTC | 245 |
| Sep 2, 2026, 5:46 PM UTC | 245 |
| Sep 2, 2026, 5:50 PM UTC | 231 |
| Sep 2, 2026, 5:54 PM UTC | 244 |
| Sep 2, 2026, 5:59 PM UTC | 251 |
| Sep 2, 2026, 6:04 PM UTC | 248 |
| Sep 2, 2026, 6:08 PM UTC | 256 |
| Sep 2, 2026, 6:11 PM UTC | 189 |
| Sep 2, 2026, 6:17 PM UTC | 254 |
| Sep 2, 2026, 6:21 PM UTC | 242 |
| Sep 2, 2026, 6:25 PM UTC | 238 |
| Sep 2, 2026, 6:29 PM UTC | 256 |
| Sep 2, 2026, 6:34 PM UTC | 241 |
| Sep 2, 2026, 6:40 PM UTC | 266 |
| Sep 2, 2026, 6:44 PM UTC | 270 |
| Sep 2, 2026, 6:48 PM UTC | 303 |
| Sep 2, 2026, 6:51 PM UTC | 258 |
| Sep 2, 2026, 6:55 PM UTC | 254 |
| Sep 2, 2026, 6:59 PM UTC | 280 |
| Sep 2, 2026, 7:04 PM UTC | 290 |
| Sep 2, 2026, 7:09 PM UTC | 296 |
| Sep 2, 2026, 7:12 PM UTC | 296 |
| Sep 2, 2026, 7:16 PM UTC | 280 |
| Sep 2, 2026, 7:20 PM UTC | 271 |
| Sep 2, 2026, 7:24 PM UTC | 262 |
| Sep 2, 2026, 7:29 PM UTC | 282 |
| Sep 2, 2026, 7:32 PM UTC | 276 |
| Sep 2, 2026, 7:35 PM UTC | 268 |
| Sep 2, 2026, 7:43 PM UTC | 221 |
| Sep 2, 2026, 7:46 PM UTC | 260 |
| Sep 2, 2026, 7:50 PM UTC | 242 |
| Sep 2, 2026, 7:58 PM UTC | 239 |
| Sep 2, 2026, 8:02 PM UTC | 224 |
| Sep 2, 2026, 8:06 PM UTC | 224 |
| Sep 2, 2026, 8:09 PM UTC | 220 |
| Sep 2, 2026, 8:14 PM UTC | 224 |
| Sep 2, 2026, 8:19 PM UTC | 250 |
| Sep 2, 2026, 8:24 PM UTC | 241 |
| Sep 2, 2026, 8:28 PM UTC | 221 |
| Sep 2, 2026, 8:32 PM UTC | 228 |
| Sep 2, 2026, 8:35 PM UTC | 228 |
| Sep 2, 2026, 8:40 PM UTC | 235 |
| Sep 2, 2026, 8:44 PM UTC | 231 |
| Sep 2, 2026, 8:48 PM UTC | 231 |
| Sep 2, 2026, 8:52 PM UTC | 218 |
| Sep 2, 2026, 8:55 PM UTC | 205 |
| Sep 2, 2026, 8:59 PM UTC | 226 |
| Sep 2, 2026, 9:04 PM UTC | 219 |
| Sep 2, 2026, 9:08 PM UTC | 219 |
| Sep 2, 2026, 9:11 PM UTC | 158 |
| Sep 2, 2026, 9:14 PM UTC | 206 |
| Sep 2, 2026, 9:19 PM UTC | 214 |
| Sep 2, 2026, 9:23 PM UTC | 205 |
| Sep 2, 2026, 9:26 PM UTC | 205 |
| Sep 2, 2026, 9:29 PM UTC | 208 |
| Sep 2, 2026, 9:34 PM UTC | 215 |
| Sep 2, 2026, 9:39 PM UTC | 231 |
| Sep 2, 2026, 9:40 PM UTC | 209 |
| Sep 2, 2026, 9:44 PM UTC | 209 |
| Sep 2, 2026, 9:49 PM UTC | 207 |
| Sep 2, 2026, 9:54 PM UTC | 213 |
| Sep 2, 2026, 9:59 PM UTC | 226 |
| Sep 2, 2026, 10:04 PM UTC | 191 |
| Sep 2, 2026, 10:08 PM UTC | 195 |
| Sep 2, 2026, 10:12 PM UTC | 207 |
| Sep 2, 2026, 10:16 PM UTC | 207 |
| Sep 2, 2026, 10:20 PM UTC | 184 |
| Sep 2, 2026, 10:24 PM UTC | 198 |
| Sep 2, 2026, 10:29 PM UTC | 187 |
| Sep 2, 2026, 10:34 PM UTC | 187 |
| Sep 2, 2026, 10:38 PM UTC | 187 |
| Sep 2, 2026, 10:42 PM UTC | 133 |
| Sep 2, 2026, 10:46 PM UTC | 173 |
| Sep 2, 2026, 10:50 PM UTC | 156 |
| Sep 2, 2026, 10:54 PM UTC | 149 |
| Sep 2, 2026, 10:57 PM UTC | 155 |
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 |
|---|---|---|---|---|---|
| Software and Game Development | 6h 56m | 225 | 303 | 1,560 |
How this broadcast compares
This broadcast averaged 225 viewers, 22.2% above the channel’s 30-day average of 184 viewers.
This broadcast drew a higher average audience than 79% of the 34 streams we finalised for this channel in the last 90 days.
How we measured it
- Samples collected
- 190
- Sampling coverage
- 97%
- Data confidence
- 97%
We check a live channel every few minutes rather than continuously, so these numbers are estimates built from 190 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 +22.2% versus the channel's 30-day average of 184 viewers.
Tracked since . Last updated .