Channel
Eddy the Baddy
@eddythebaddys
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,252subscribers
-435 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001948904588 |
|---|---|
| Type | Channel |
| Username | @eddythebaddys |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/eddythebaddys |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 08:46 | 5,252 | -31 |
| 4 Nov 2026, 00:39 | 5,283 | -20 |
| 1 Nov 2026, 03:17 | 5,303 | -35 |
| 29 Oct 2026, 00:10 | 5,338 | -25 |
| 25 Oct 2026, 21:39 | 5,363 | -26 |
| 23 Oct 2026, 03:55 | 5,389 | -36 |
| 20 Oct 2026, 04:37 | 5,425 | -20 |
| 17 Oct 2026, 10:29 | 5,445 | -19 |
| 14 Oct 2026, 12:10 | 5,464 | -24 |
| 11 Oct 2026, 04:58 | 5,488 | -40 |
| 5 Oct 2026, 00:37 | 5,528 | -55 |
| 25 Sept 2026, 20:02 | 5,583 | -35 |
| 15 Sept 2026, 02:00 | 5,618 | -9 |
| 11 Sept 2026, 20:01 | 5,627 | -19 |
| 7 Sept 2026, 11:21 | 5,646 | -18 |
| 2 Sept 2026, 12:45 | 5,664 | -6 |
| 30 Aug 2026, 20:36 | 5,670 | -15 |
| 30 Aug 2026, 18:28 | 5,685 | no change |
| 27 Aug 2026, 18:18 | 5,685 | -2 |
| 27 Aug 2026, 02:45 | 5,687 | 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.
@forsageio_official · 33,708
Telegram ranks this channel #1 of 21 here — alongside 20 others — read 2 September 2026
@MetaProSpaceofficialchannel · 18,389
Telegram ranks this channel #16 of 25 here — alongside 24 others — read 30 September 2026
@teenpattiking777 · 17,575
Telegram ranks this channel #33 of 34 here — alongside 33 others — read 2 October 2026
@metawhale · 44,674
Telegram ranks this channel #70 of 84 here — alongside 83 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Eddy the Baddy” (@eddythebaddys), 5,252 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/eddythebaddys.
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.