Channel
Tahminfelsefesi
@thmnfelsefesi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
17,590subscribers
-1,174 since we began measuring on 12 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002064750763 |
|---|---|
| Type | Channel |
| Username | @thmnfelsefesi |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/thmnfelsefesi |
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 4 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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, 19:40 | 17,590 | -15 |
| 30 Oct 2026, 22:35 | 17,605 | -30 |
| 29 Oct 2026, 20:00 | 17,635 | -15 |
| 28 Oct 2026, 17:40 | 17,650 | -6 |
| 27 Oct 2026, 20:40 | 17,656 | -6 |
| 26 Oct 2026, 22:36 | 17,662 | -14 |
| 25 Oct 2026, 19:47 | 17,676 | -11 |
| 24 Oct 2026, 20:27 | 17,687 | -15 |
| 23 Oct 2026, 19:46 | 17,702 | -19 |
| 22 Oct 2026, 17:58 | 17,721 | -18 |
| 21 Oct 2026, 13:38 | 17,739 | -23 |
| 20 Oct 2026, 13:50 | 17,762 | -17 |
| 19 Oct 2026, 11:10 | 17,779 | -16 |
| 18 Oct 2026, 11:06 | 17,795 | -13 |
| 17 Oct 2026, 14:29 | 17,808 | -20 |
| 16 Oct 2026, 16:19 | 17,828 | -13 |
| 15 Oct 2026, 13:49 | 17,841 | -18 |
| 14 Oct 2026, 11:14 | 17,859 | -35 |
| 12 Oct 2026, 22:56 | 17,894 | -93 |
| 8 Oct 2026, 13:55 | 17,987 | 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 #14 of 53 here — alongside 52 others — read 12 September 2026
@blazecanli · 21,004
Telegram ranks this channel #15 of 48 here — alongside 47 others — read 21 September 2026
@iddia_analiz_kupon · 32,376
Telegram ranks this channel #28 of 47 here — alongside 46 others — read 12 September 2026
@atakancanlive · 21,652
Telegram ranks this channel #38 of 50 here — alongside 49 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“Tahminfelsefesi” (@thmnfelsefesi), 17,590 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/thmnfelsefesi.
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.