Telegram RegisterThe public register of Telegram
Telegram profile photo for HAMSHIRA_jurnali. ๐‘ซ๐‘ด๐‘ฌ๐‘ซ ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ ๐‘ฝ๐‘จ ๐‘จ๐‘ฒ๐‘ป ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ๐‘ฎ๐‘จ ๐‘ฉ๐‘ฌ๐‘ท๐‘ผ๐‘ณ ๐‘ป๐‘จ๐’€๐’€๐‘ถ๐‘น๐‘ณ๐‘จ๐’€๐‘ด๐‘ฐ๐’!

Channel

HAMSHIRA_jurnali. ๐‘ซ๐‘ด๐‘ฌ๐‘ซ ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ ๐‘ฝ๐‘จ ๐‘จ๐‘ฒ๐‘ป ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ๐‘ฎ๐‘จ ๐‘ฉ๐‘ฌ๐‘ท๐‘ผ๐‘ณ ๐‘ป๐‘จ๐’€๐’€๐‘ถ๐‘น๐‘ณ๐‘จ๐’€๐‘ด๐‘ฐ๐’!

@ssv_hamshira_jurn

Has discussion group

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

5,110subscribers

-149 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
TypeChannel
Username@ssv_hamshira_jurn
CreatedBetween 1 January 2022 and 31 March 2023 โ€” estimated from Telegramโ€™s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live6 November 2026
Measurements held18
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.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 the other topics.

Growth

5,1105,2595,184.51 September 2026 โ€” 5,259 subscribers1 September 2026 โ€” 5,259 subscribers1 September 2026 โ€” 5,251 subscribers5 September 2026 โ€” 5,254 subscribers10 September 2026 โ€” 5,245 subscribers14 September 2026 โ€” 5,229 subscribers19 September 2026 โ€” 5,211 subscribers29 September 2026 โ€” 5,199 subscribers6 October 2026 โ€” 5,172 subscribers13 October 2026 โ€” 5,154 subscribers16 October 2026 โ€” 5,161 subscribers19 October 2026 โ€” 5,155 subscribers22 October 2026 โ€” 5,148 subscribers25 October 2026 โ€” 5,131 subscribers28 October 2026 โ€” 5,113 subscribers31 October 2026 โ€” 5,120 subscribers3 November 2026 โ€” 5,116 subscribers6 November 2026 โ€” 5,110 subscribers1 September 20266 November 2026
18 measurements spanning 66 days, net -149. 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 5,088โ€“5,281 and does not start at zero.
Measurement log โ€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 10:165,110-6
3 Nov 2026, 10:505,116-4
31 Oct 2026, 12:205,120+7
28 Oct 2026, 16:095,113-18
25 Oct 2026, 14:465,131-17
22 Oct 2026, 17:355,148-7
19 Oct 2026, 10:385,155-6
16 Oct 2026, 08:265,161+7
13 Oct 2026, 00:575,154-18
6 Oct 2026, 16:195,172-27
29 Sept 2026, 14:375,199-12
19 Sept 2026, 10:205,211-18
14 Sept 2026, 16:555,229-16
10 Sept 2026, 19:165,245-9
5 Sept 2026, 22:595,254+3
1 Sept 2026, 21:595,251-8
1 Sept 2026, 11:465,259no change
1 Sept 2026, 03:455,259first 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 ยท 81,470
Telegram ranks this channel #4 of 52 here โ€” alongside 51 others โ€” read 1 September 2026
Hamshiralarga ๐ŸŒน(Testlar)
@hamshiralarga ยท 42,235
Telegram ranks this channel #5 of 58 here โ€” alongside 57 others โ€” read 18 September 2026
ะฅะฐะผัˆะธั€ะฐ ั‚ะตัั‚ ะš-ะฑะพะทะพั€
@qbozor_medical ยท 81,379
Telegram ranks this channel #5 of 38 here โ€” alongside 37 others โ€” read 1 September 2026
TOIFA JAVOBLARI โš•๏ธ
@toifa_javoblari ยท 59,374
Telegram ranks this channel #10 of 58 here โ€” alongside 57 others โ€” read 1 September 2026
Tibbiyot haqida
@tibbiyot_haqida ยท 55,815
Telegram ranks this channel #16 of 59 here โ€” alongside 58 others โ€” read 1 September 2026
TibbiyotTv | OperatsiyaUzB
@tibbiyottv ยท 22,584
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 6 November 2026 โ€” this entry's latest reading, not the date you are reading this.

โ€œHAMSHIRA_jurnali. ๐‘ซ๐‘ด๐‘ฌ๐‘ซ ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ ๐‘ฝ๐‘จ ๐‘จ๐‘ฒ๐‘ป ๐‘ป๐‘ฌ๐‘บ๐‘ป๐‘ณ๐‘จ๐‘น๐‘ฐ๐‘ฎ๐‘จ ๐‘ฉ๐‘ฌ๐‘ท๐‘ผ๐‘ณ ๐‘ป๐‘จ๐’€๐’€๐‘ถ๐‘น๐‘ณ๐‘จ๐’€๐‘ด๐‘ฐ๐’!โ€ (@ssv_hamshira_jurn), 5,110 subscribers as measured 6 November 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.