Channel
برق صنعتی
@barghtech_official
On this record: Topic · Previous handles · Growth · Engagement · Telegram's recommendations · Cite this entry
3,572subscribers
+117 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001894601220 |
|---|---|
| Type | Channel |
| Username | @barghtech_official |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/barghtech_official |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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.
Previous handles
@barghtech_official was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 8 September 2026 – 8 September 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 01:40 | 3,572 | +11 |
| 3 Oct 2026, 00:01 | 3,561 | no change |
| 2 Oct 2026, 22:47 | 3,561 | +27 |
| 12 Sept 2026, 22:18 | 3,534 | +7 |
| 9 Sept 2026, 08:36 | 3,527 | +13 |
| 8 Sept 2026, 00:24 | 3,514 | no change |
| 4 Sept 2026, 01:16 | 3,514 | +13 |
| 31 Aug 2026, 13:25 | 3,501 | +4 |
| 28 Aug 2026, 09:33 | 3,497 | +6 |
| 25 Aug 2026, 04:07 | 3,491 | +5 |
| 22 Aug 2026, 07:35 | 3,486 | +5 |
| 19 Aug 2026, 04:55 | 3,481 | +20 |
| 16 Aug 2026, 15:06 | 3,461 | +2 |
| 10 Aug 2026, 15:27 | 3,459 | -1 |
| 7 Aug 2026, 16:30 | 3,460 | +5 |
| 7 Aug 2026, 04:15 | 3,455 | 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.
@bargheeha · 21,001
Telegram ranks this channel #10 of 64 here — alongside 63 others — read 25 September 2026
@electronicghodrat · 19,291
Telegram ranks this channel #21 of 72 here — alongside 71 others — read 2 October 2026
This channel appears in 2 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 October 2026 — this entry's latest reading, not the date you are reading this.
“برق صنعتی” (@barghtech_official), 3,572 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/barghtech_official.
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.