Channel
@aloneaddict
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
19,309subscribers
-348 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001567460066 |
|---|---|
| Type | Channel |
| Username | @aloneaddict |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/aloneaddict |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 12:41 | 19,309 | -15 |
| 2 Sept 2026, 07:37 | 19,324 | -16 |
| 1 Sept 2026, 04:14 | 19,340 | -17 |
| 31 Aug 2026, 05:36 | 19,357 | -17 |
| 30 Aug 2026, 08:36 | 19,374 | -15 |
| 29 Aug 2026, 05:36 | 19,389 | -16 |
| 28 Aug 2026, 04:38 | 19,405 | -15 |
| 27 Aug 2026, 04:34 | 19,420 | -13 |
| 26 Aug 2026, 01:04 | 19,433 | -17 |
| 24 Aug 2026, 23:34 | 19,450 | -31 |
| 23 Aug 2026, 07:07 | 19,481 | -42 |
| 21 Aug 2026, 18:08 | 19,523 | -16 |
| 20 Aug 2026, 12:52 | 19,539 | -24 |
| 19 Aug 2026, 13:24 | 19,563 | -26 |
| 18 Aug 2026, 15:14 | 19,589 | -18 |
| 17 Aug 2026, 17:08 | 19,607 | -32 |
| 16 Aug 2026, 08:55 | 19,639 | -18 |
| 15 Aug 2026, 12:15 | 19,657 | no change |
| 15 Aug 2026, 12:02 | 19,657 | first reading |
20 posts held, back to 25 March 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 15 February 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 20 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
🔥மகா சிவராத்திரி 💥 NEW TREND EDIT 😍 உங்களுக்கு சாங்ஸ் புடிச்சிருந்தா தயவுசெய்து உங்களுக்குப் பிடித்த Emoji குடுங்க அடுத்த சாங்ஸ் போடறதுக்கு எனக்கு ஆதரவாக இருக்கும் 👇 Emoji👇
Downfall is Set for Comeback 📈🔥
Oru maalai ❤️✨ Tag Ur Luv 💕 More :- @AloneAddict
Naan Nee 💜✨ Tag Ur Luv 💕 More :- @AloneAddict
Nee 🤍✨💫 Tag Ur Luv 💕 More :- @AloneAddict
Kelambu 🥰🤭.. Tag Ur Luv 💕 More :- @AloneAddict
Engayum kadhal 💕 Tag Ur Luv ❤️✨ More :- @AloneAddict
She is My Everything ❤️ Tag Ur Luv 💕 More :- @AloneAddict
Udaintheney 🚶🏻❤️🩹 HD status ✨ More :- @AloneAddict
Poongatre ❤️✨ Tag Ur Luv 💕 More :- @AloneAddict
Kanimozhiye 🦋❤️🩹 Tag Ur Luv 💕 More :- @AloneAddict
Kadhal Aasai 🤍✨ Tag Ur Luv 💕 More :- @AloneAddict
Showing the 12 most recent of 20 posts we hold for @aloneaddict. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
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.
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“𝘼𝙡𝙤𝙣𝙚 𝘼𝙙𝙙𝙞𝙘𝙩 ™” (@aloneaddict), 19,309 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/aloneaddict.
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.