
Channel
دوازدهم |بلدستون
@Baladestoon12
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,717subscribers
-104 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 | -1002225833712 |
|---|---|
| Type | Channel |
| Username | @Baladestoon12 |
| Description | بلدستون کنارتونه❤️🌱 🌱جهت ارتباط با ما: @SigmaAdmin |
| First recorded | 24 September 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 13 |
| On Telegram | t.me/Baladestoon12 |
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 24 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Sept 2026, 15:49 | 1,717 | no change |
| 19 Sept 2026, 15:40 | 1,717 | -7 |
| 14 Sept 2026, 23:38 | 1,724 | -6 |
| 11 Sept 2026, 09:36 | 1,730 | -18 |
| 6 Sept 2026, 20:18 | 1,748 | -20 |
| 2 Sept 2026, 07:56 | 1,768 | -9 |
| 30 Aug 2026, 08:49 | 1,777 | -9 |
| 27 Aug 2026, 12:47 | 1,786 | -7 |
| 24 Aug 2026, 22:23 | 1,793 | -8 |
| 21 Aug 2026, 04:29 | 1,801 | -10 |
| 18 Aug 2026, 00:22 | 1,811 | -7 |
| 14 Aug 2026, 22:04 | 1,818 | -3 |
| 13 Aug 2026, 19:30 | 1,821 | 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.
@yazdahom · 121,234
Telegram ranks this channel #2 of 85 here — alongside 84 others — read 13 August 2026
@bombriazi1401 · 39,321
Telegram ranks this channel #3 of 79 here — alongside 78 others — read 30 August 2026
@alireza_tajabadi · 52,480
Telegram ranks this channel #4 of 58 here — alongside 57 others — read 25 August 2026
@bonyad_nohomihaa · 25,759
Telegram ranks this channel #9 of 55 here — alongside 54 others — read 14 September 2026
@barge_sefiid · 25,461
Telegram ranks this channel #19 of 74 here — alongside 73 others — read 17 September 2026
@Mser_12 · 28,995
Telegram ranks this channel #46 of 75 here — alongside 74 others — read 8 September 2026
@Nohomiun · 36,299
Telegram ranks this channel #49 of 77 here — alongside 76 others — read 1 September 2026
This channel appears in 7 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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“دوازدهم |بلدستون” (@Baladestoon12), 1,717 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/Baladestoon12.
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.