Telegram RegisterThe public register of Telegram
Telegram profile photo for Kureelu xasida yi micro 🎤 ❤️🤍

Channel

Kureelu xasida yi micro 🎤 ❤️🤍

@ndiagoumkourelkhasida

Has discussion group

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

4,275subscribers

+79 since we began measuring on 4 September 2026

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

Register entry

Telegram ID-1001715983313
TypeChannel
Username@ndiagoumkourelkhasida
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/ndiagoumkourelkhasida

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

4,1964,2754,235.54 September 2026 — 4,196 subscribers4 September 2026 — 4,196 subscribers6 September 2026 — 4,225 subscribers11 September 2026 — 4,252 subscribers15 September 2026 — 4,256 subscribers19 September 2026 — 4,275 subscribers4 September 202619 September 2026
6 measurements spanning 15 days, net +79. 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 4,184–4,287 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:594,275+19
15 Sept 2026, 08:584,256+4
11 Sept 2026, 13:014,252+27
6 Sept 2026, 11:384,225+29
4 Sept 2026, 22:024,196no change
4 Sept 2026, 03:474,196first 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Khassida Yi Rék
@khassidaYiReik · 33,744
Telegram ranks this channel #9 of 72 here — alongside 71 others — read 4 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Kureelu xasida yi micro 🎤 ❤️🤍” (@ndiagoumkourelkhasida), 4,275 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ndiagoumkourelkhasida.

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.