
Channel
InTheMoon ✧
@ilosemyselfinthesongs
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,352subscribers
-24 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002184056089 |
|---|---|
| Type | Channel |
| Username | @ilosemyselfinthesongs |
| Description | I luv u, but u don’t understand me🦢 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/ilosemyselfinthesongs |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 01:04 | 2,352 | no change |
| 16 Sept 2026, 01:59 | 2,352 | +1 |
| 12 Sept 2026, 14:02 | 2,351 | +1 |
| 8 Sept 2026, 22:22 | 2,350 | -12 |
| 3 Sept 2026, 13:58 | 2,362 | -6 |
| 31 Aug 2026, 06:07 | 2,368 | -2 |
| 27 Aug 2026, 22:25 | 2,370 | -4 |
| 24 Aug 2026, 15:29 | 2,374 | -5 |
| 20 Aug 2026, 14:44 | 2,379 | +5 |
| 17 Aug 2026, 20:37 | 2,374 | -2 |
| 17 Aug 2026, 13:15 | 2,376 | 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.
@gzllammm · 40,344
Telegram ranks this channel #35 of 35 here — alongside 34 others — read 24 September 2026
@staw999 · 51,758
Telegram ranks this channel #36 of 38 here — alongside 37 others — read 26 August 2026
@soogowu · 97,408
Telegram ranks this channel #36 of 45 here — alongside 44 others — read 17 August 2026
@selenatel · 22,146
Telegram ranks this channel #39 of 47 here — alongside 46 others — read 21 September 2026
@diyanamrh · 53,348
Telegram ranks this channel #41 of 49 here — alongside 48 others — read 25 August 2026
@setayeshhwj · 157,416
Telegram ranks this channel #42 of 45 here — alongside 44 others — read 25 August 2026
@urcloudi2222 · 74,177
Telegram ranks this channel #50 of 51 here — alongside 50 others — read 20 August 2026
This channel appears in 7 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“InTheMoon ✧” (@ilosemyselfinthesongs), 2,352 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ilosemyselfinthesongs.
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.