Telegram RegisterThe public register of Telegram
Telegram profile photo for βšœπ‘€π‘œπ‘™π‘œπ‘‘π‘’π‘§β„Žπ‘›π‘¦π‘’ π‘‘π‘Ÿπ‘’π‘˜π‘– 𝟸𝟢𝟸𝟼⚜

Channel

βšœπ‘€π‘œπ‘™π‘œπ‘‘π‘’π‘§β„Žπ‘›π‘¦π‘’ π‘‘π‘Ÿπ‘’π‘˜π‘– 𝟸𝟢𝟸𝟼⚜

@Taven_bakhtale_761

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

3,375subscribers

+51 since we began measuring on 7 August 2026

Risers and fallers across the register Β· movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001641778771
TypeChannel
Username@Taven_bakhtale_761
CreatedBetween 1 December 2021 and 30 April 2023 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live13 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 13 October 2026
On Telegramt.me/Taven_bakhtale_761

Topic

Other / unclassifiable β€” 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 14 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 why it has no browse page of its own yet.

Growth

3,3163,3793,347.57 August 2026 β€” 3,324 subscribers11 August 2026 β€” 3,330 subscribers14 August 2026 β€” 3,326 subscribers17 August 2026 β€” 3,325 subscribers21 August 2026 β€” 3,317 subscribers24 August 2026 β€” 3,316 subscribers27 August 2026 β€” 3,325 subscribers30 August 2026 β€” 3,327 subscribers2 September 2026 β€” 3,330 subscribers6 September 2026 β€” 3,348 subscribers9 September 2026 β€” 3,348 subscribers11 September 2026 β€” 3,357 subscribers15 September 2026 β€” 3,369 subscribers19 September 2026 β€” 3,374 subscribers29 September 2026 β€” 3,375 subscribers6 October 2026 β€” 3,379 subscribers13 October 2026 β€” 3,375 subscribers3,3757 August 202613 October 2026
17 measurements spanning 67 days, net +51. 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”. The vertical axis spans 3,307–3,388 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 02:273,375-4
6 Oct 2026, 18:203,379+4
29 Sept 2026, 14:153,375+1
19 Sept 2026, 16:563,374+5
15 Sept 2026, 11:173,369+12
11 Sept 2026, 11:403,357+9
9 Sept 2026, 00:243,348no change
6 Sept 2026, 22:353,348+18
2 Sept 2026, 06:133,330+3
30 Aug 2026, 10:153,327+2
27 Aug 2026, 13:553,325+9
24 Aug 2026, 11:193,316-1
21 Aug 2026, 01:253,317-8
17 Aug 2026, 16:573,325-1
14 Aug 2026, 20:253,326-4
11 Aug 2026, 01:273,330+6
7 Aug 2026, 13:393,324first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured β€” we do not publish a rate before we have the readings behind 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 13 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œβšœπ‘€π‘œπ‘™π‘œπ‘‘π‘’π‘§β„Žπ‘›π‘¦π‘’ π‘‘π‘Ÿπ‘’π‘˜π‘– πŸΈπŸΆπŸΈπŸΌβšœβ€ (@Taven_bakhtale_761), 3,375 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/Taven_bakhtale_761.

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.