Channel
Superb Safety Engineers's Library
@HSEProfessional2784
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,225subscribers
+12 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001392009248 |
|---|---|
| Type | Channel |
| Username | @HSEProfessional2784 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/HSEProfessional2784 |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 18 Oct 2026, 07:37 | 7,225 | +1 |
| 15 Oct 2026, 14:10 | 7,224 | +7 |
| 12 Oct 2026, 21:28 | 7,217 | +3 |
| 6 Oct 2026, 04:18 | 7,214 | +3 |
| 29 Sept 2026, 01:00 | 7,211 | -18 |
| 19 Sept 2026, 10:00 | 7,229 | +9 |
| 14 Sept 2026, 23:40 | 7,220 | +7 |
| 13 Sept 2026, 14:58 | 7,213 | no change |
| 13 Sept 2026, 14:47 | 7,213 | 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.
@metallurgical_engineering007 · 21,595
Telegram ranks this channel #16 of 67 here — alongside 66 others — read 22 September 2026
@pipingengineeringworld · 21,349
Telegram ranks this channel #29 of 75 here — alongside 74 others — read 23 September 2026
@whatispiping · 22,820
Telegram ranks this channel #29 of 78 here — alongside 77 others — read 19 September 2026
@education2342 · 21,033
Telegram ranks this channel #59 of 63 here — alongside 62 others — read 23 September 2026
@OilAndGas · 26,112
Telegram ranks this channel #76 of 79 here — alongside 78 others — read 13 September 2026
@Chem_Eng_World · 19,537
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 2 October 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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“Superb Safety Engineers's Library” (@HSEProfessional2784), 7,225 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/HSEProfessional2784.
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.