Channel
ДЖАДД PRO HEALTH
@djaddpro
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,753subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001516938231 |
|---|---|
| Type | Channel |
| Username | @djaddpro |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/djaddpro |
Topic
Health & wellness — 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 24 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 07:19 | 1,753 | -2 |
| 24 Sept 2026, 01:36 | 1,755 | no change |
| 15 Sept 2026, 04:59 | 1,755 | +4 |
| 12 Sept 2026, 00:19 | 1,751 | +1 |
| 7 Sept 2026, 14:21 | 1,750 | -12 |
| 2 Sept 2026, 16:53 | 1,762 | +4 |
| 30 Aug 2026, 22:04 | 1,758 | +2 |
| 27 Aug 2026, 14:03 | 1,756 | +2 |
| 24 Aug 2026, 19:56 | 1,754 | +1 |
| 21 Aug 2026, 09:56 | 1,753 | -1 |
| 18 Aug 2026, 11:33 | 1,754 | +1 |
| 15 Aug 2026, 01:46 | 1,753 | +1 |
| 11 Aug 2026, 17:48 | 1,752 | -3 |
| 7 Aug 2026, 13:16 | 1,755 | 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.
@doclana_mornatural · 31,685
Telegram ranks this channel #27 of 80 here — alongside 79 others — read 6 September 2026
@detsdoc · 59,048
Telegram ranks this channel #28 of 91 here — alongside 90 others — read 22 August 2026
@doctor_alina_enikeeva · 24,412
Telegram ranks this channel #30 of 81 here — alongside 80 others — read 16 September 2026
@humberto_2_0 · 20,949
Telegram ranks this channel #39 of 88 here — alongside 87 others — read 25 September 2026
@annacheeta · 33,816
Telegram ranks this channel #64 of 90 here — alongside 89 others — read 3 September 2026
@zdravomislievede · 31,536
Telegram ranks this channel #74 of 97 here — alongside 96 others — read 6 September 2026
This channel appears in 6 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“ДЖАДД PRO HEALTH” (@djaddpro), 1,753 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/djaddpro.
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.