Channel
@civil_engineering_update
On this record: Topic · Growth · Engagement · Posts · Cite this entry
279subscribers
+71 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003892702147 |
|---|---|
| Type | Channel |
| Username | @civil_engineering_update |
| Created | Between 1 February 2026 and 30 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/civil_engineering_update |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 15:36 | 279 | -2 |
| 28 Sept 2026, 06:38 | 281 | +45 |
| 13 Sept 2026, 21:17 | 236 | +23 |
| 29 Aug 2026, 05:22 | 213 | +2 |
| 21 Aug 2026, 07:44 | 211 | -1 |
| 14 Aug 2026, 23:14 | 212 | +4 |
| 8 Aug 2026, 11:05 | 208 | no change |
| 7 Aug 2026, 18:58 | 208 | first reading |
20 posts held, back to 2 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
🌉 Why Do Roads Have Small Gaps Around Bridges? That small gap is not a construction defect—it allows the bridge to move safely. Bridge decks expand when temperatures rise and contract when temperatures fall. They may also move slightly due to traffic loads, concrete shrinkage, creep and foundation movement. Temperature change \bm{\rightarrow} Bridge movement \bm{\rightarrow} Expansion gap accommodates movement If the…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 20 posts we hold for @civil_engineering_update. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“Civil engineering updates” (@civil_engineering_update), 279 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/civil_engineering_update.
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.