Channel
Deliibal__
@delibalsr
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,830subscribers
-124 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 | -1001915127558 |
|---|---|
| Type | Channel |
| Username | @delibalsr |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/delibalsr |
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 15 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 18:26 | 2,830 | -1 |
| 3 Nov 2026, 23:48 | 2,831 | -2 |
| 31 Oct 2026, 17:37 | 2,833 | -3 |
| 28 Oct 2026, 23:51 | 2,836 | -6 |
| 26 Oct 2026, 02:44 | 2,842 | -4 |
| 22 Oct 2026, 18:57 | 2,846 | -2 |
| 19 Oct 2026, 05:09 | 2,848 | -5 |
| 16 Oct 2026, 07:16 | 2,853 | -8 |
| 12 Oct 2026, 23:49 | 2,861 | -8 |
| 6 Oct 2026, 22:39 | 2,869 | -3 |
| 29 Sept 2026, 20:37 | 2,872 | -37 |
| 16 Sept 2026, 02:41 | 2,909 | -10 |
| 12 Sept 2026, 02:57 | 2,919 | -8 |
| 12 Sept 2026, 00:33 | 2,927 | no change |
| 7 Sept 2026, 15:38 | 2,927 | -4 |
| 2 Sept 2026, 09:53 | 2,931 | -4 |
| 27 Aug 2026, 05:19 | 2,935 | -5 |
| 24 Aug 2026, 10:16 | 2,940 | -3 |
| 20 Aug 2026, 11:54 | 2,943 | -5 |
| 17 Aug 2026, 18:39 | 2,948 | first 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.
@khoone_gandom · 22,063
Telegram ranks this channel #20 of 69 here — alongside 68 others — read 20 September 2026
@bioshick · 27,031
Telegram ranks this channel #31 of 64 here — alongside 63 others — read 10 September 2026
@minii_shear · 55,292
Telegram ranks this channel #37 of 77 here — alongside 76 others — read 24 August 2026
@tunesgraphy · 139,262
Telegram ranks this channel #60 of 72 here — alongside 71 others — read 13 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“Deliibal__” (@delibalsr), 2,830 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/delibalsr.
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.