Channel
Yalçın Öğretmen
@yalcinogretmen
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
10,658subscribers
+365 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 | -1001289103939 |
|---|---|
| Type | Channel |
| Username | @yalcinogretmen |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 30 October 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 30 October 2026 |
| On Telegram | t.me/yalcinogretmen |
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 67% 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 |
|---|---|---|
| 30 Oct 2026, 21:28 | 10,658 | +12 |
| 29 Oct 2026, 23:06 | 10,646 | +1 |
| 28 Oct 2026, 22:20 | 10,645 | +14 |
| 27 Oct 2026, 22:38 | 10,631 | +17 |
| 26 Oct 2026, 21:05 | 10,614 | +6 |
| 25 Oct 2026, 23:07 | 10,608 | +12 |
| 24 Oct 2026, 23:15 | 10,596 | +6 |
| 23 Oct 2026, 20:28 | 10,590 | +7 |
| 22 Oct 2026, 20:59 | 10,583 | +19 |
| 21 Oct 2026, 20:37 | 10,564 | +16 |
| 20 Oct 2026, 19:08 | 10,548 | +48 |
| 19 Oct 2026, 15:30 | 10,500 | +9 |
| 18 Oct 2026, 15:50 | 10,491 | -5 |
| 17 Oct 2026, 15:08 | 10,496 | -1 |
| 16 Oct 2026, 17:35 | 10,497 | +4 |
| 15 Oct 2026, 18:30 | 10,493 | +2 |
| 14 Oct 2026, 15:46 | 10,491 | +6 |
| 13 Oct 2026, 06:44 | 10,485 | +1 |
| 9 Oct 2026, 03:20 | 10,484 | +6 |
| 4 Oct 2026, 16:35 | 10,478 | 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.
@ilkokuletkinliklerm · 21,366
Telegram ranks this channel #4 of 66 here — alongside 65 others — read 27 September 2026
@sorogretmenim · 33,245
Telegram ranks this channel #6 of 72 here — alongside 71 others — read 12 September 2026
@webdeogrenkanal · 24,096
Telegram ranks this channel #18 of 68 here — alongside 67 others — read 16 September 2026
@mebduyurulari1 · 18,524
Telegram ranks this channel #27 of 70 here — alongside 69 others — read 3 October 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 30 October 2026 — this entry's latest reading, not the date you are reading this.
“Yalçın Öğretmen” (@yalcinogretmen), 10,658 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/yalcinogretmen.
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.