Channel
HİSSE HANE BİRLİĞİ
@hissehanee
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,317subscribers
-43 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002105172718 |
|---|---|
| Type | Channel |
| Username | @hissehanee |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/hissehanee |
Topic
Crypto & trading — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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 |
|---|---|---|
| 5 Nov 2026, 21:48 | 2,317 | -9 |
| 2 Nov 2026, 16:45 | 2,326 | -15 |
| 31 Oct 2026, 01:18 | 2,341 | -7 |
| 27 Oct 2026, 22:19 | 2,348 | -2 |
| 24 Oct 2026, 20:48 | 2,350 | +9 |
| 22 Oct 2026, 05:46 | 2,341 | -2 |
| 18 Oct 2026, 20:56 | 2,343 | -12 |
| 15 Oct 2026, 14:28 | 2,355 | -12 |
| 12 Oct 2026, 21:20 | 2,367 | -10 |
| 6 Oct 2026, 16:55 | 2,377 | -18 |
| 29 Sept 2026, 14:56 | 2,395 | +9 |
| 16 Sept 2026, 22:28 | 2,386 | no change |
| 15 Sept 2026, 21:18 | 2,386 | +8 |
| 12 Sept 2026, 14:17 | 2,378 | -4 |
| 8 Sept 2026, 18:01 | 2,382 | +10 |
| 3 Sept 2026, 09:36 | 2,372 | -14 |
| 31 Aug 2026, 02:22 | 2,386 | -3 |
| 28 Aug 2026, 06:13 | 2,389 | +13 |
| 25 Aug 2026, 06:55 | 2,376 | -1 |
| 22 Aug 2026, 08:45 | 2,377 | 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.
@borsaefendisi1111 · 44,776
Telegram ranks this channel #2 of 65 here — alongside 64 others — read 27 August 2026
@FxSpaceGlobal · 255,028
Telegram ranks this channel #12 of 73 here — alongside 72 others — read 18 August 2026
@arzduyurum · 67,111
Telegram ranks this channel #28 of 63 here — alongside 62 others — read 2 September 2026
@halka_arz1 · 468,465
Telegram ranks this channel #28 of 84 here — alongside 83 others — read 18 August 2026
@borsa_halkaarz_haber · 70,178
Telegram ranks this channel #34 of 59 here — alongside 58 others — read 18 August 2026
This channel appears in 5 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“HİSSE HANE BİRLİĞİ” (@hissehanee), 2,317 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/hissehanee.
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.