Channel
latakia structural designer
@latakia_structural_designer
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,962subscribers
+4 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001471590752 |
|---|---|
| Type | Channel |
| Username | @latakia_structural_designer |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/latakia_structural_designer |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 05:25 | 1,962 | +2 |
| 31 Oct 2026, 10:10 | 1,960 | +3 |
| 25 Oct 2026, 19:17 | 1,957 | +2 |
| 23 Oct 2026, 00:30 | 1,955 | -2 |
| 20 Oct 2026, 09:50 | 1,957 | +1 |
| 17 Oct 2026, 17:09 | 1,956 | -2 |
| 15 Oct 2026, 00:28 | 1,958 | -1 |
| 5 Oct 2026, 10:57 | 1,959 | -2 |
| 27 Sept 2026, 16:19 | 1,961 | -1 |
| 21 Sept 2026, 02:50 | 1,962 | no change |
| 18 Sept 2026, 14:59 | 1,962 | +4 |
| 14 Sept 2026, 17:55 | 1,958 | -2 |
| 11 Sept 2026, 00:36 | 1,960 | -3 |
| 6 Sept 2026, 11:19 | 1,963 | -1 |
| 1 Sept 2026, 20:15 | 1,964 | -1 |
| 30 Aug 2026, 06:27 | 1,965 | +2 |
| 23 Aug 2026, 21:04 | 1,963 | +5 |
| 20 Aug 2026, 14:45 | 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.
@bimsociety · 24,651
Telegram ranks this channel #12 of 65 here — alongside 64 others — read 16 September 2026
@new_AmeerAlborihi_library · 94,202
Telegram ranks this channel #24 of 69 here — alongside 68 others — read 29 August 2026
@Tleeq · 32,756
Telegram ranks this channel #29 of 63 here — alongside 62 others — read 5 September 2026
@drmajidalbana · 31,789
Telegram ranks this channel #30 of 83 here — alongside 82 others — read 5 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“latakia structural designer” (@latakia_structural_designer), 1,962 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/latakia_structural_designer.
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.