Channel
Concrete Channel
@Concrete_Engineering_Services
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
10,381subscribers
+11 since we began measuring on 29 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001176977429 |
|---|---|
| Type | Channel |
| Username | @Concrete_Engineering_Services |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Concrete_Engineering_Services |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 19 Sept 2026, 12:55 | 10,381 | -2 |
| 16 Sept 2026, 21:40 | 10,383 | +5 |
| 15 Sept 2026, 00:57 | 10,378 | +6 |
| 13 Sept 2026, 09:01 | 10,372 | +1 |
| 11 Sept 2026, 13:40 | 10,371 | -1 |
| 8 Sept 2026, 19:21 | 10,372 | +2 |
| 3 Sept 2026, 10:26 | 10,370 | -2 |
| 2 Sept 2026, 05:43 | 10,372 | -2 |
| 1 Sept 2026, 07:06 | 10,374 | +5 |
| 31 Aug 2026, 04:24 | 10,369 | +1 |
| 30 Aug 2026, 06:08 | 10,368 | -2 |
| 29 Aug 2026, 23:05 | 10,370 | 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.
@civilacademy2023 · 22,546
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 20 September 2026
@WALIDSAIED · 36,461
Telegram ranks this channel #4 of 76 here — alongside 75 others — read 1 September 2026
@new_AmeerAlborihi_library · 94,233
Telegram ranks this channel #13 of 69 here — alongside 68 others — read 29 August 2026
@sa3edmohamed1 · 36,559
Telegram ranks this channel #23 of 74 here — alongside 73 others — read 1 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Concrete Channel” (@Concrete_Engineering_Services), 10,381 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Concrete_Engineering_Services.
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.