Channel
piping Engineering Team
@pipingengineering
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,998subscribers
+40 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001003864011 |
|---|---|
| Type | Channel |
| Username | @pipingengineering |
| Description | @pipingengineering كانال تخصصي پايپينگ و پايپ لاين مطالب كاربردي و آموزشي |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 21 September 2026 |
| Measurements held | 15 |
| On Telegram | t.me/pipingengineering |
Topic
Education — 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 21 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 |
|---|---|---|
| 21 Sept 2026, 01:07 | 1,998 | no change |
| 15 Sept 2026, 11:21 | 1,998 | +5 |
| 11 Sept 2026, 15:20 | 1,993 | +7 |
| 7 Sept 2026, 01:20 | 1,986 | +4 |
| 2 Sept 2026, 08:26 | 1,982 | +1 |
| 30 Aug 2026, 10:27 | 1,981 | +3 |
| 27 Aug 2026, 15:13 | 1,978 | +3 |
| 25 Aug 2026, 00:27 | 1,975 | +3 |
| 21 Aug 2026, 06:16 | 1,972 | +2 |
| 18 Aug 2026, 06:12 | 1,970 | +7 |
| 14 Aug 2026, 21:27 | 1,963 | +1 |
| 11 Aug 2026, 18:03 | 1,962 | +1 |
| 9 Aug 2026, 04:21 | 1,961 | +1 |
| 6 Aug 2026, 14:20 | 1,960 | +2 |
| 5 Aug 2026, 19:06 | 1,958 | 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.
@OilAndGas · 25,946
Telegram ranks this channel #21 of 79 here — alongside 78 others — read 13 September 2026
@Good_morning_wish_Quotes_Lines · 32,072
Telegram ranks this channel #23 of 49 here — alongside 48 others — read 5 September 2026
@SakhtoTolidi · 21,649
Telegram ranks this channel #28 of 69 here — alongside 68 others — read 23 September 2026
@whatispiping · 22,827
Telegram ranks this channel #39 of 78 here — alongside 77 others — read 19 September 2026
@cad_3d · 22,395
Telegram ranks this channel #59 of 79 here — alongside 78 others — read 20 September 2026
This channel appears in 5 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 21 September 2026 — this entry's latest reading, not the date you are reading this.
“piping Engineering Team” (@pipingengineering), 1,998 subscribers as measured 21 September 2026. Telegram Register, tgregister.com/channel/pipingengineering.
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.