Channel
💢متنهای درخشان عاشقی💢
@ebiLove20
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,096subscribers
+76 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001285788855 |
|---|---|
| Type | Channel |
| Username | @ebiLove20 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/ebiLove20 |
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 7 October 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 4 Nov 2026, 07:36 | 1,096 | +1 |
| 1 Nov 2026, 05:37 | 1,095 | +6 |
| 28 Oct 2026, 19:40 | 1,089 | +4 |
| 25 Oct 2026, 10:00 | 1,085 | -2 |
| 22 Oct 2026, 12:07 | 1,087 | -3 |
| 19 Oct 2026, 03:37 | 1,090 | +5 |
| 12 Oct 2026, 17:28 | 1,085 | +4 |
| 7 Oct 2026, 04:43 | 1,081 | no change |
| 6 Oct 2026, 12:18 | 1,081 | +3 |
| 29 Sept 2026, 22:17 | 1,078 | +12 |
| 15 Sept 2026, 16:15 | 1,066 | +11 |
| 12 Sept 2026, 01:19 | 1,055 | +3 |
| 7 Sept 2026, 18:00 | 1,052 | +10 |
| 2 Sept 2026, 13:23 | 1,042 | +3 |
| 30 Aug 2026, 22:54 | 1,039 | +5 |
| 28 Aug 2026, 05:04 | 1,034 | +4 |
| 25 Aug 2026, 07:12 | 1,030 | +8 |
| 22 Aug 2026, 09:58 | 1,022 | +1 |
| 19 Aug 2026, 01:34 | 1,021 | +1 |
| 18 Aug 2026, 12:45 | 1,020 | 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.
@nabtarin_tex · 27,358
Telegram ranks this channel #6 of 75 here — alongside 74 others — read 11 September 2026
@mitingg · 50,634
Telegram ranks this channel #28 of 70 here — alongside 69 others — read 22 August 2026
@Tahavol_nab · 82,586
Telegram ranks this channel #32 of 88 here — alongside 87 others — read 18 August 2026
@haghi43 · 46,141
Telegram ranks this channel #53 of 78 here — alongside 77 others — read 27 August 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“💢متنهای درخشان عاشقی💢” (@ebiLove20), 1,096 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ebiLove20.
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.