Channel
Control Engineering
@ControlEngineering98
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,302subscribers
+65 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 | -1001767797832 |
|---|---|
| Type | Channel |
| Username | @ControlEngineering98 |
| Description | جهت ارتباط با ادمینها، به گروه کانال مراجعه کنین. https://t.me/+k1OZ6I6uW5YzY2I8 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/ControlEngineering98 |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 40% 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 |
|---|---|---|
| 17 Sept 2026, 15:26 | 2,302 | no change |
| 15 Sept 2026, 07:37 | 2,302 | +3 |
| 11 Sept 2026, 09:58 | 2,299 | +7 |
| 6 Sept 2026, 16:20 | 2,292 | +9 |
| 2 Sept 2026, 01:27 | 2,283 | +10 |
| 29 Aug 2026, 23:04 | 2,273 | -5 |
| 27 Aug 2026, 08:15 | 2,278 | +6 |
| 24 Aug 2026, 11:13 | 2,272 | +9 |
| 20 Aug 2026, 23:14 | 2,263 | +3 |
| 17 Aug 2026, 12:43 | 2,260 | +13 |
| 14 Aug 2026, 13:36 | 2,247 | +10 |
| 11 Aug 2026, 07:43 | 2,237 | +1 |
| 8 Aug 2026, 09:08 | 2,236 | -1 |
| 7 Aug 2026, 19:35 | 2,237 | 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.
@RMS_English · 52,475
Telegram ranks this channel #43 of 84 here — alongside 83 others — read 24 August 2026
@JOZVEGAH · 97,360
Telegram ranks this channel #64 of 87 here — alongside 86 others — read 16 August 2026
@publictabrizuniversity · 22,460
Telegram ranks this channel #71 of 94 here — alongside 93 others — read 20 September 2026
@Tabriz_university_students · 22,936
Telegram ranks this channel #71 of 91 here — alongside 90 others — read 19 September 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Control Engineering” (@ControlEngineering98), 2,302 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ControlEngineering98.
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.