
Channel
رمان یک هیچ به او باختم🔥
@yekhichbeobakhtam
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,862subscribers
-202 since we began measuring on 30 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001798289854 |
|---|---|
| Type | Channel |
| Username | @yekhichbeobakhtam |
| Created | Between 1 February 2022 and 31 January 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/yekhichbeobakhtam |
Topic
Literature — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 14 Nov 2026, 12:49 | 3,862 | -3 |
| 9 Nov 2026, 10:37 | 3,865 | -4 |
| 5 Nov 2026, 17:54 | 3,869 | -10 |
| 2 Nov 2026, 13:11 | 3,879 | -13 |
| 30 Oct 2026, 12:34 | 3,892 | -5 |
| 27 Oct 2026, 05:49 | 3,897 | +2 |
| 24 Oct 2026, 07:45 | 3,895 | -11 |
| 21 Oct 2026, 17:41 | 3,906 | -2 |
| 18 Oct 2026, 22:21 | 3,908 | -5 |
| 16 Oct 2026, 00:08 | 3,913 | -9 |
| 13 Oct 2026, 05:30 | 3,922 | -29 |
| 6 Oct 2026, 17:37 | 3,951 | -19 |
| 29 Sept 2026, 20:00 | 3,970 | -46 |
| 16 Sept 2026, 00:18 | 4,016 | -14 |
| 11 Sept 2026, 21:36 | 4,030 | -16 |
| 7 Sept 2026, 20:19 | 4,046 | -11 |
| 5 Sept 2026, 12:41 | 4,057 | no change |
| 2 Sept 2026, 23:18 | 4,057 | -8 |
| 30 Aug 2026, 13:25 | 4,065 | +1 |
| 30 Aug 2026, 10:45 | 4,064 | 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.
@avayekhis · 45,789
Telegram ranks this channel #1 of 78 here — alongside 77 others — read 30 August 2026
@httpsTelesmat_ghasemi · 84,554
Telegram ranks this channel #40 of 69 here — alongside 68 others — read 7 September 2026
@RMNHUB · 682
Telegram ranks this channel #68 of 75 here — alongside 74 others — read 27 September 2026
@caffetakroman · 29,572
Telegram ranks this channel #80 of 82 here — alongside 81 others — read 7 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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“رمان یک هیچ به او باختم🔥” (@yekhichbeobakhtam), 3,862 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/yekhichbeobakhtam.
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.