Channel
شاقول/ایموشن کد/ای اف تی
@shaghol_eft_bahareh_rezaei
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,262subscribers
+36 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002172267855 |
|---|---|
| Type | Channel |
| Username | @shaghol_eft_bahareh_rezaei |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/shaghol_eft_bahareh_rezaei |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 74% 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 |
|---|---|---|
| 4 Nov 2026, 07:50 | 1,262 | -1 |
| 1 Nov 2026, 11:56 | 1,263 | +6 |
| 29 Oct 2026, 14:31 | 1,257 | -2 |
| 26 Oct 2026, 15:45 | 1,259 | -3 |
| 20 Oct 2026, 16:16 | 1,262 | +1 |
| 17 Oct 2026, 20:51 | 1,261 | +5 |
| 15 Oct 2026, 06:55 | 1,256 | -1 |
| 11 Oct 2026, 23:54 | 1,257 | +5 |
| 5 Oct 2026, 06:54 | 1,252 | +4 |
| 3 Oct 2026, 03:41 | 1,248 | no change |
| 26 Sept 2026, 17:00 | 1,248 | +6 |
| 17 Sept 2026, 07:55 | 1,242 | +2 |
| 13 Sept 2026, 18:41 | 1,240 | +5 |
| 10 Sept 2026, 04:21 | 1,235 | +2 |
| 4 Sept 2026, 20:37 | 1,233 | +3 |
| 1 Sept 2026, 01:05 | 1,230 | +4 |
| 27 Aug 2026, 21:15 | 1,226 | 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.
@z1m2y3 · 36,018
Telegram ranks this channel #26 of 63 here — alongside 62 others — read 1 September 2026
@AshkanHoriyat_Rabete · 31,912
Telegram ranks this channel #34 of 65 here — alongside 64 others — read 4 September 2026
@drzarifi_podcast · 20,626
Telegram ranks this channel #35 of 67 here — alongside 66 others — read 25 September 2026
@fatemeh_jafarnia · 44,103
Telegram ranks this channel #53 of 67 here — alongside 66 others — read 27 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“شاقول/ایموشن کد/ای اف تی” (@shaghol_eft_bahareh_rezaei), 1,262 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/shaghol_eft_bahareh_rezaei.
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.