Telegram RegisterThe public register of Telegram
Telegram profile photo for Kino

Channel

Kino

@KinoBIuray

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

13subscribers

-62,916 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002236689023
TypeChannel
Username@KinoBIuray
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 November 2026
Measurements held50
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/KinoBIuray

Topic

Film & TV — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

265,56532,783.58 August 2026 — 62,929 subscribers9 August 2026 — 62,524 subscribers10 August 2026 — 61,946 subscribers11 August 2026 — 62,085 subscribers11 August 2026 — 62,085 subscribers12 August 2026 — 61,818 subscribers13 August 2026 — 61,398 subscribers14 August 2026 — 60,704 subscribers15 August 2026 — 60,576 subscribers17 August 2026 — 59,988 subscribers18 August 2026 — 59,643 subscribers19 August 2026 — 59,182 subscribers20 August 2026 — 59,390 subscribers21 August 2026 — 60,304 subscribers22 August 2026 — 61,311 subscribers24 August 2026 — 61,105 subscribers25 August 2026 — 61,545 subscribers26 August 2026 — 61,607 subscribers27 August 2026 — 61,485 subscribers28 August 2026 — 61,113 subscribers29 August 2026 — 60,699 subscribers30 August 2026 — 60,595 subscribers31 August 2026 — 60,929 subscribers1 September 2026 — 61,118 subscribers2 September 2026 — 60,927 subscribers3 September 2026 — 60,535 subscribers5 September 2026 — 60,248 subscribers8 September 2026 — 60,572 subscribers11 September 2026 — 59,481 subscribers13 September 2026 — 59,099 subscribers14 September 2026 — 58,572 subscribers16 September 2026 — 58,343 subscribers18 September 2026 — 57,928 subscribers2 October 2026 — 62,102 subscribers7 October 2026 — 62,380 subscribers11 October 2026 — 65,565 subscribers14 October 2026 — 64,582 subscribers15 October 2026 — 64,193 subscribers16 October 2026 — 63,866 subscribers17 October 2026 — 63,690 subscribers18 October 2026 — 63,413 subscribers19 October 2026 — 63,175 subscribers20 October 2026 — 62,452 subscribers21 October 2026 — 61,892 subscribers22 October 2026 — 62,084 subscribers23 October 2026 — 61,991 subscribers24 October 2026 — 61,820 subscribers25 October 2026 — 2 subscribers1 November 2026 — 12 subscribers10 November 2026 — 13 subscribers138 August 202610 November 2026
50 measurements spanning 94 days, net -62,916. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 50
Measured (UTC)SubscribersChange
10 Nov 2026, 11:4713+1
1 Nov 2026, 23:0412+10
25 Oct 2026, 11:192-61,818
24 Oct 2026, 12:4061,820-171
23 Oct 2026, 10:1161,991-93
22 Oct 2026, 12:2062,084+192
21 Oct 2026, 09:1961,892-560
20 Oct 2026, 05:4062,452-723
19 Oct 2026, 04:1063,175-238
18 Oct 2026, 02:4663,413-277
17 Oct 2026, 05:0763,690-176
16 Oct 2026, 06:0163,866-327
15 Oct 2026, 07:4764,193-389
14 Oct 2026, 03:5164,582-983
11 Oct 2026, 21:3765,565+3,185
7 Oct 2026, 08:2062,380+278
2 Oct 2026, 12:3662,102+4,174
18 Sept 2026, 16:1557,928-415
16 Sept 2026, 11:4158,343-229
14 Sept 2026, 17:0258,572first reading

Engagement

No public post preview. We read this entry on 11 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Kino” (@KinoBIuray), 13 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/KinoBIuray.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.