Channel
HAMSHIRA_jurnali. ๐ซ๐ด๐ฌ๐ซ ๐ป๐ฌ๐บ๐ป๐ณ๐จ๐น๐ฐ ๐ฝ๐จ ๐จ๐ฒ๐ป ๐ป๐ฌ๐บ๐ป๐ณ๐จ๐น๐ฐ๐ฎ๐จ ๐ฉ๐ฌ๐ท๐ผ๐ณ ๐ป๐จ๐๐๐ถ๐น๐ณ๐จ๐๐ด๐ฐ๐!
@ssv_hamshira_jurn
On this record: Topic ยท Growth ยท Engagement ยท Telegram's recommendations ยท Cite this entry
5,211subscribers
-48 since we began measuring on 1 September 2026
Risers and fallers across the register ยท movement among entries of 3,162โ10,000.
Register entry
| Telegram ID | -1001792695131 |
|---|---|
| Type | Channel |
| Username | @ssv_hamshira_jurn |
| Created | Between 1 January 2022 and 28 February 2023 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/ssv_hamshira_jurn |
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 68% 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 |
|---|---|---|
| 19 Sept 2026, 10:20 | 5,211 | -18 |
| 14 Sept 2026, 16:55 | 5,229 | -16 |
| 10 Sept 2026, 19:16 | 5,245 | -9 |
| 5 Sept 2026, 22:59 | 5,254 | +3 |
| 1 Sept 2026, 21:59 | 5,251 | -8 |
| 1 Sept 2026, 11:46 | 5,259 | no change |
| 1 Sept 2026, 03:45 | 5,259 | 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.
@xamshiralaruchun ยท 82,144
Telegram ranks this channel #4 of 52 here โ alongside 51 others โ read 1 September 2026
@hamshiralarga ยท 42,686
Telegram ranks this channel #5 of 58 here โ alongside 57 others โ read 18 September 2026
@qbozor_medical ยท 79,974
Telegram ranks this channel #5 of 38 here โ alongside 37 others โ read 1 September 2026
@toifa_javoblari ยท 58,485
Telegram ranks this channel #10 of 58 here โ alongside 57 others โ read 1 September 2026
@tibbiyot_haqida ยท 57,582
Telegram ranks this channel #16 of 59 here โ alongside 58 others โ read 1 September 2026
@tibbiyottv ยท 23,464
Telegram ranks this channel #33 of 47 here โ alongside 46 others โ read 18 September 2026
This channel appears in 6 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 19 September 2026 โ this entry's latest reading, not the date you are reading this.
โHAMSHIRA_jurnali. ๐ซ๐ด๐ฌ๐ซ ๐ป๐ฌ๐บ๐ป๐ณ๐จ๐น๐ฐ ๐ฝ๐จ ๐จ๐ฒ๐ป ๐ป๐ฌ๐บ๐ป๐ณ๐จ๐น๐ฐ๐ฎ๐จ ๐ฉ๐ฌ๐ท๐ผ๐ณ ๐ป๐จ๐๐๐ถ๐น๐ณ๐จ๐๐ด๐ฐ๐!โ (@ssv_hamshira_jurn), 5,211 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ssv_hamshira_jurn.
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.