Channel
self l🤍ve
@self1oveclub
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,061subscribers
+200 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002040180181 |
|---|---|
| Type | Channel |
| Username | @self1oveclub |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/self1oveclub |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 7 Nov 2026, 00:30 | 4,061 | +6 |
| 4 Nov 2026, 00:47 | 4,055 | +4 |
| 31 Oct 2026, 15:14 | 4,051 | -2 |
| 25 Oct 2026, 20:09 | 4,053 | -2 |
| 22 Oct 2026, 17:36 | 4,055 | +1 |
| 19 Oct 2026, 04:36 | 4,054 | +2 |
| 15 Oct 2026, 20:48 | 4,052 | +5 |
| 12 Oct 2026, 16:08 | 4,047 | +17 |
| 6 Oct 2026, 03:38 | 4,030 | +85 |
| 29 Sept 2026, 06:39 | 3,945 | +82 |
| 19 Sept 2026, 15:21 | 3,863 | -11 |
| 15 Sept 2026, 06:57 | 3,874 | -4 |
| 12 Sept 2026, 01:00 | 3,878 | -6 |
| 7 Sept 2026, 21:40 | 3,884 | +1 |
| 6 Sept 2026, 00:07 | 3,883 | no change |
| 2 Sept 2026, 20:45 | 3,883 | +1 |
| 30 Aug 2026, 19:34 | 3,882 | +3 |
| 28 Aug 2026, 02:08 | 3,879 | +12 |
| 25 Aug 2026, 02:32 | 3,867 | +6 |
| 23 Aug 2026, 23:30 | 3,861 | 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.
@spring_v1bes · 21,333
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 19 September 2026
@cozyy_channel · 49,446
Telegram ranks this channel #17 of 59 here — alongside 58 others — read 23 August 2026
@maria_elita · 23,141
Telegram ranks this channel #40 of 68 here — alongside 67 others — read 21 September 2026
@wonygysm · 21,888
Telegram ranks this channel #40 of 50 here — alongside 49 others — read 19 September 2026
@engwwz · 19,292
Telegram ranks this channel #59 of 77 here — alongside 76 others — read 1 October 2026
This channel appears in 5 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“self l🤍ve” (@self1oveclub), 4,061 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/self1oveclub.
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.