Channel
الأمن الصحي
@HealthSecurity4
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,247subscribers
+16 since we began measuring on 3 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001729854674 |
|---|---|
| Type | Channel |
| Username | @HealthSecurity4 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/HealthSecurity4 |
Topic
Religion — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 5 Nov 2026, 14:55 | 2,247 | +3 |
| 2 Nov 2026, 12:44 | 2,244 | +3 |
| 30 Oct 2026, 17:29 | 2,241 | -5 |
| 27 Oct 2026, 11:35 | 2,246 | -1 |
| 24 Oct 2026, 14:10 | 2,247 | -2 |
| 21 Oct 2026, 14:16 | 2,249 | +3 |
| 18 Oct 2026, 14:40 | 2,246 | -7 |
| 15 Oct 2026, 07:49 | 2,253 | +2 |
| 12 Oct 2026, 11:47 | 2,251 | +6 |
| 5 Oct 2026, 09:56 | 2,245 | +5 |
| 27 Sept 2026, 02:01 | 2,240 | +3 |
| 18 Sept 2026, 02:01 | 2,237 | no change |
| 17 Sept 2026, 16:55 | 2,237 | +2 |
| 13 Sept 2026, 16:17 | 2,235 | +3 |
| 9 Sept 2026, 12:18 | 2,232 | +2 |
| 4 Sept 2026, 14:41 | 2,230 | -1 |
| 3 Sept 2026, 21:17 | 2,231 | 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.
@iAhmedMoh · 33,857
Telegram ranks this channel #3 of 68 here — alongside 67 others — read 3 September 2026
@AskJusur · 28,492
Telegram ranks this channel #6 of 73 here — alongside 72 others — read 9 September 2026
@leadermr101 · 29,037
Telegram ranks this channel #40 of 86 here — alongside 85 others — read 9 September 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“الأمن الصحي” (@HealthSecurity4), 2,247 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/HealthSecurity4.
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.