Channel
HALKA ARZ BORSA
@halkaarzborsaaa
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,126subscribers
-331 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001711175937 |
|---|---|
| Type | Channel |
| Username | @halkaarzborsaaa |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/halkaarzborsaaa |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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, 20:06 | 4,126 | -19 |
| 2 Nov 2026, 09:45 | 4,145 | -15 |
| 30 Oct 2026, 14:00 | 4,160 | -14 |
| 27 Oct 2026, 11:46 | 4,174 | -13 |
| 24 Oct 2026, 11:50 | 4,187 | -19 |
| 21 Oct 2026, 15:58 | 4,206 | -16 |
| 18 Oct 2026, 02:09 | 4,222 | -18 |
| 15 Oct 2026, 09:37 | 4,240 | -18 |
| 12 Oct 2026, 16:39 | 4,258 | -35 |
| 6 Oct 2026, 04:36 | 4,293 | -36 |
| 29 Sept 2026, 02:41 | 4,329 | -37 |
| 16 Sept 2026, 07:57 | 4,366 | -9 |
| 12 Sept 2026, 22:38 | 4,375 | -8 |
| 8 Sept 2026, 19:20 | 4,383 | -28 |
| 3 Sept 2026, 22:22 | 4,411 | no change |
| 3 Sept 2026, 01:57 | 4,411 | -12 |
| 30 Aug 2026, 22:24 | 4,423 | -19 |
| 28 Aug 2026, 05:15 | 4,442 | -4 |
| 25 Aug 2026, 01:56 | 4,446 | -3 |
| 21 Aug 2026, 11:35 | 4,449 | 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.
@arz_bilgiler · 26,010
Telegram ranks this channel #3 of 73 here — alongside 72 others — read 10 September 2026
@halka_arz3 · 62,735
Telegram ranks this channel #22 of 71 here — alongside 70 others — read 20 August 2026
@Borsa_Hisse_Haber · 34,302
Telegram ranks this channel #40 of 73 here — alongside 72 others — read 25 August 2026
@GercekCemalBuyukkardes · 20,194
Telegram ranks this channel #41 of 67 here — alongside 66 others — read 26 September 2026
This channel appears in 4 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.
“HALKA ARZ BORSA” (@halkaarzborsaaa), 4,126 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/halkaarzborsaaa.
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.