Channel
DAY TRADER TELUGU 🔷
@DAY_TRADER_TELUGU_35
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,565subscribers
-52 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001858738295 |
|---|---|
| Type | Channel |
| Username | @DAY_TRADER_TELUGU_35 |
| Created | Between 1 October 2022 and 30 September 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/DAY_TRADER_TELUGU_35 |
Topic
Crypto & trading — 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 74% 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, 09:46 | 5,565 | -4 |
| 30 Oct 2026, 08:10 | 5,569 | -7 |
| 24 Oct 2026, 13:00 | 5,576 | -2 |
| 14 Oct 2026, 21:39 | 5,578 | -11 |
| 11 Oct 2026, 05:15 | 5,589 | -9 |
| 5 Oct 2026, 05:42 | 5,598 | -8 |
| 26 Sept 2026, 22:40 | 5,606 | -2 |
| 15 Sept 2026, 19:38 | 5,608 | -3 |
| 11 Sept 2026, 21:57 | 5,611 | +5 |
| 7 Sept 2026, 16:35 | 5,606 | -2 |
| 3 Sept 2026, 04:17 | 5,608 | -1 |
| 31 Aug 2026, 09:54 | 5,609 | +1 |
| 30 Aug 2026, 21:28 | 5,608 | no change |
| 28 Aug 2026, 20:37 | 5,608 | +1 |
| 25 Aug 2026, 10:38 | 5,607 | -3 |
| 22 Aug 2026, 04:45 | 5,610 | -2 |
| 18 Aug 2026, 11:57 | 5,612 | -3 |
| 15 Aug 2026, 07:35 | 5,615 | -1 |
| 11 Aug 2026, 20:24 | 5,616 | -1 |
| 11 Aug 2026, 15:15 | 5,617 | 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.
@PTS_PRABHAT_TRADING_SERVICES_3 · 41,628
Telegram ranks this channel #4 of 42 here — alongside 41 others — read 24 August 2026
@DAY_TRADER_TELUGU_38 · 213,693
Telegram ranks this channel #6 of 45 here — alongside 44 others — read 11 August 2026
@day_trader_telugu_36 · 47,074
Telegram ranks this channel #10 of 44 here — alongside 43 others — read 25 August 2026
This channel appears in 3 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.
“DAY TRADER TELUGU 🔷” (@DAY_TRADER_TELUGU_35), 5,565 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/DAY_TRADER_TELUGU_35.
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.