Telegram RegisterThe public register of Telegram
Telegram profile photo for 🎵 XIT TARONALAR

Channel

🎵 XIT TARONALAR

@taronalar_xit_2026

Has discussion group

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

2,058subscribers

-182 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001195619590
TypeChannel
Username@taronalar_xit_2026
Created10 November 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded19 September 2026
Last confirmed live10 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/taronalar_xit_2026

Topic

Music — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

2,0582,2412,149.513 August 2026 — 2,240 subscribers13 August 2026 — 2,241 subscribers17 August 2026 — 2,225 subscribers20 August 2026 — 2,215 subscribers23 August 2026 — 2,200 subscribers26 August 2026 — 2,192 subscribers29 August 2026 — 2,180 subscribers1 September 2026 — 2,166 subscribers6 September 2026 — 2,149 subscribers11 September 2026 — 2,137 subscribers15 September 2026 — 2,132 subscribers19 September 2026 — 2,132 subscribers25 September 2026 — 2,107 subscribers4 October 2026 — 2,072 subscribers10 October 2026 — 2,058 subscribers13 August 202610 October 2026
15 measurements spanning 59 days, net -182. 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 2,031–2,268 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 21:382,058-14
4 Oct 2026, 19:552,072-35
25 Sept 2026, 00:582,107-25
19 Sept 2026, 15:122,132no change
15 Sept 2026, 11:382,132-5
11 Sept 2026, 12:012,137-12
6 Sept 2026, 17:592,149-17
1 Sept 2026, 23:282,166-14
29 Aug 2026, 17:282,180-12
26 Aug 2026, 12:252,192-8
23 Aug 2026, 09:032,200-15
20 Aug 2026, 06:242,215-10
17 Aug 2026, 10:332,225-16
13 Aug 2026, 09:572,241+1
13 Aug 2026, 02:322,240first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 October 2026 — this entry's latest reading, not the date you are reading this.

“🎵 XIT TARONALAR” (@taronalar_xit_2026), 2,058 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/taronalar_xit_2026.

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.