Channel
352 Taktik
@taktik352
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,278subscribers
-237 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002070565189 |
|---|---|
| Type | Channel |
| Username | @taktik352 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/taktik352 |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 31 Oct 2026, 20:38 | 5,278 | -24 |
| 28 Oct 2026, 12:31 | 5,302 | -6 |
| 25 Oct 2026, 02:54 | 5,308 | -14 |
| 21 Oct 2026, 21:55 | 5,322 | -1 |
| 18 Oct 2026, 07:30 | 5,323 | -14 |
| 14 Oct 2026, 22:15 | 5,337 | -15 |
| 11 Oct 2026, 08:35 | 5,352 | -29 |
| 5 Oct 2026, 03:02 | 5,381 | -37 |
| 26 Sept 2026, 05:36 | 5,418 | -56 |
| 17 Sept 2026, 03:56 | 5,474 | -24 |
| 13 Sept 2026, 10:39 | 5,498 | -17 |
| 11 Sept 2026, 23:50 | 5,515 | 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.
@bellagioanalysis · 37,361
Telegram ranks this channel #1 of 53 here — alongside 52 others — read 12 September 2026
@blazecanli · 21,004
Telegram ranks this channel #2 of 48 here — alongside 47 others — read 21 September 2026
@Bahis_Tahminler_Casino · 38,858
Telegram ranks this channel #13 of 34 here — alongside 33 others — read 12 September 2026
@magicosman · 35,218
Telegram ranks this channel #18 of 49 here — alongside 48 others — read 11 September 2026
@atakancanlive · 21,652
Telegram ranks this channel #20 of 50 here — alongside 49 others — read 26 September 2026
@iddaakosesitv · 23,881
Telegram ranks this channel #28 of 53 here — alongside 52 others — read 17 September 2026
@iddia_analiz_kupon · 32,376
Telegram ranks this channel #45 of 47 here — alongside 46 others — read 12 September 2026
This channel appears in 7 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“352 Taktik” (@taktik352), 5,278 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/taktik352.
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.