北斗卡門 — stream on October 3, 2026
20261003 再戰新竹任務Uber eat Day2 跑一整天看看能不能進帳2000 好撈明天再住一晚
Started · 14h 38m · 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.
- IRL01:26–16:05
View as table
| Time (UTC) | Viewers |
|---|---|
| Oct 3, 2026, 1:49 AM UTC | 142 |
| Oct 3, 2026, 1:58 AM UTC | 176 |
| Oct 3, 2026, 2:11 AM UTC | 225 |
| Oct 3, 2026, 2:24 AM UTC | 274 |
| Oct 3, 2026, 2:38 AM UTC | 300 |
| Oct 3, 2026, 2:49 AM UTC | 285 |
| Oct 3, 2026, 2:57 AM UTC | 293 |
| Oct 3, 2026, 3:05 AM UTC | 287 |
| Oct 3, 2026, 3:14 AM UTC | 307 |
| Oct 3, 2026, 3:24 AM UTC | 312 |
| Oct 3, 2026, 3:34 AM UTC | 328 |
| Oct 3, 2026, 3:44 AM UTC | 329 |
| Oct 3, 2026, 3:51 AM UTC | 330 |
| Oct 3, 2026, 3:59 AM UTC | 351 |
| Oct 3, 2026, 4:08 AM UTC | 333 |
| Oct 3, 2026, 4:15 AM UTC | 345 |
| Oct 3, 2026, 4:27 AM UTC | 303 |
| Oct 3, 2026, 4:38 AM UTC | 334 |
| Oct 3, 2026, 4:44 AM UTC | 344 |
| Oct 3, 2026, 4:54 AM UTC | 350 |
| Oct 3, 2026, 5:04 AM UTC | 379 |
| Oct 3, 2026, 5:13 AM UTC | 353 |
| Oct 3, 2026, 5:24 AM UTC | 359 |
| Oct 3, 2026, 5:32 AM UTC | 366 |
| Oct 3, 2026, 5:42 AM UTC | 366 |
| Oct 3, 2026, 5:49 AM UTC | 357 |
| Oct 3, 2026, 5:59 AM UTC | 362 |
| Oct 3, 2026, 6:07 AM UTC | 359 |
| Oct 3, 2026, 6:15 AM UTC | 331 |
| Oct 3, 2026, 6:24 AM UTC | 349 |
| Oct 3, 2026, 6:31 AM UTC | 377 |
| Oct 3, 2026, 6:42 AM UTC | 388 |
| Oct 3, 2026, 6:49 AM UTC | 384 |
| Oct 3, 2026, 6:59 AM UTC | 363 |
| Oct 3, 2026, 7:09 AM UTC | 387 |
| Oct 3, 2026, 7:19 AM UTC | 367 |
| Oct 3, 2026, 7:28 AM UTC | 343 |
| Oct 3, 2026, 7:35 AM UTC | 347 |
| Oct 3, 2026, 7:44 AM UTC | 353 |
| Oct 3, 2026, 7:52 AM UTC | 361 |
| Oct 3, 2026, 8:03 AM UTC | 346 |
| Oct 3, 2026, 8:11 AM UTC | 355 |
| Oct 3, 2026, 8:22 AM UTC | 357 |
| Oct 3, 2026, 8:29 AM UTC | 344 |
| Oct 3, 2026, 8:39 AM UTC | 337 |
| Oct 3, 2026, 8:49 AM UTC | 345 |
| Oct 3, 2026, 8:57 AM UTC | 357 |
| Oct 3, 2026, 9:04 AM UTC | 335 |
| Oct 3, 2026, 9:14 AM UTC | 331 |
| Oct 3, 2026, 9:24 AM UTC | 329 |
| Oct 3, 2026, 9:32 AM UTC | 338 |
| Oct 3, 2026, 9:44 AM UTC | 317 |
| Oct 3, 2026, 9:52 AM UTC | 304 |
| Oct 3, 2026, 10:00 AM UTC | 323 |
| Oct 3, 2026, 10:09 AM UTC | 322 |
| Oct 3, 2026, 10:18 AM UTC | 342 |
| Oct 3, 2026, 10:25 AM UTC | 349 |
| Oct 3, 2026, 10:34 AM UTC | 353 |
| Oct 3, 2026, 10:43 AM UTC | 376 |
| Oct 3, 2026, 10:51 AM UTC | 355 |
| Oct 3, 2026, 10:59 AM UTC | 338 |
| Oct 3, 2026, 11:08 AM UTC | 354 |
| Oct 3, 2026, 11:16 AM UTC | 353 |
| Oct 3, 2026, 11:24 AM UTC | 359 |
| Oct 3, 2026, 11:34 AM UTC | 352 |
| Oct 3, 2026, 11:44 AM UTC | 350 |
| Oct 3, 2026, 11:53 AM UTC | 330 |
| Oct 3, 2026, 12:00 PM UTC | 339 |
| Oct 3, 2026, 12:09 PM UTC | 353 |
| Oct 3, 2026, 12:19 PM UTC | 353 |
| Oct 3, 2026, 12:26 PM UTC | 353 |
| Oct 3, 2026, 12:38 PM UTC | 369 |
| Oct 3, 2026, 12:44 PM UTC | 365 |
| Oct 3, 2026, 12:50 PM UTC | 365 |
| Oct 3, 2026, 12:59 PM UTC | 352 |
| Oct 3, 2026, 1:07 PM UTC | 370 |
| Oct 3, 2026, 1:14 PM UTC | 358 |
| Oct 3, 2026, 1:23 PM UTC | 372 |
| Oct 3, 2026, 1:29 PM UTC | 375 |
| Oct 3, 2026, 1:39 PM UTC | 371 |
| Oct 3, 2026, 1:48 PM UTC | 368 |
| Oct 3, 2026, 1:58 PM UTC | 370 |
| Oct 3, 2026, 2:06 PM UTC | 364 |
| Oct 3, 2026, 2:14 PM UTC | 400 |
| Oct 3, 2026, 2:24 PM UTC | 403 |
| Oct 3, 2026, 2:31 PM UTC | 386 |
| Oct 3, 2026, 2:41 PM UTC | 376 |
| Oct 3, 2026, 2:49 PM UTC | 435 |
| Oct 3, 2026, 2:58 PM UTC | 410 |
| Oct 3, 2026, 3:04 PM UTC | 419 |
| Oct 3, 2026, 3:14 PM UTC | 411 |
| Oct 3, 2026, 3:24 PM UTC | 411 |
| Oct 3, 2026, 3:33 PM UTC | 399 |
| Oct 3, 2026, 3:41 PM UTC | 407 |
| Oct 3, 2026, 3:49 PM UTC | 413 |
| Oct 3, 2026, 3:59 PM UTC | 377 |
| Oct 3, 2026, 4:03 PM UTC | 359 |
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 |
|---|---|---|---|---|---|
| IRL | 14h 38m | 348 | 435 | 5,089 |
How this broadcast compares
This broadcast averaged 348 viewers, 13.5% above the channel’s 30-day average of 306 viewers.
This broadcast drew a higher average audience than 90% of the 51 streams we finalised for this channel in the last 90 days.
How we measured it
- Samples collected
- 383
- Sampling coverage
- 98%
- Data confidence
- 98%
We check a live channel every few minutes rather than continuously, so these numbers are estimates built from 383 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 +13.5% versus the channel's 30-day average of 306 viewers.
- Among the top 10% of this channel's tracked streams by average viewership.
Tracked since . Last updated .