Channel
@GD16k
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
15,030subscribers
-269 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001931202479 |
|---|---|
| Type | Channel |
| Username | @GD16k |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/GD16k |
Literature — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 25 Sept 2026, 18:00 | 15,030 | -34 |
| 19 Sept 2026, 04:17 | 15,064 | +1 |
| 16 Sept 2026, 19:58 | 15,063 | -11 |
| 14 Sept 2026, 21:41 | 15,074 | -11 |
| 13 Sept 2026, 10:57 | 15,085 | -6 |
| 11 Sept 2026, 11:20 | 15,091 | -33 |
| 8 Sept 2026, 18:01 | 15,124 | -15 |
| 5 Sept 2026, 11:17 | 15,139 | -11 |
| 3 Sept 2026, 15:20 | 15,150 | -8 |
| 2 Sept 2026, 09:43 | 15,158 | -1 |
| 1 Sept 2026, 07:26 | 15,159 | -15 |
| 31 Aug 2026, 08:06 | 15,174 | -17 |
| 30 Aug 2026, 05:15 | 15,191 | -13 |
| 29 Aug 2026, 01:48 | 15,204 | -11 |
| 28 Aug 2026, 04:55 | 15,215 | +5 |
| 27 Aug 2026, 07:03 | 15,210 | -7 |
| 26 Aug 2026, 06:28 | 15,217 | -4 |
| 25 Aug 2026, 03:53 | 15,221 | -3 |
| 23 Aug 2026, 22:25 | 15,224 | -20 |
| 22 Aug 2026, 05:36 | 15,244 | first reading |
44 posts held, back to 17 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 52 pages 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 44 posts for this entry, the most recent from 18 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
مَا كُنْتُ أَهْجُرُكَ الجَفَاءَ وَإِنَّمَا نَأَيْتُ صَوْنًا لِمُهْجَتِي مِنْ وَجْدِي أَخْفَيْتُ وَجْدِي وَالوَجِيبُ مُفَضِّحِي وَتَسَتَّرَتْ بِالسَّكْنَةِ أَضْلَاعِي مَا زَالَ طَيْفُكَ فِي خَفَايَا خَاطِرِي يَسْرِي كَسِرٍّ غَائِرٍ فِي أَعْمَاقِي مَا خَابَ حُبِّي لَكِنْ خِفْتُ أَنْ أَرَى فِي قُرْبِكَ الآتِيَ ضَيَاعَ بَقَائِي فَنَأَيْتُ وَالنَّأْيُ المُرُّ أَرْحَمُ لِي مِنْ قُرْبِكَ الَّذِي اسْتَبَاحَ شَغَافِي وَلَوْ ع…
Photo, posted without a caption
متابيع المصلحه
Signed زَهُّر
ضايجه عود
Signed زَهُّر
شنو نروح
Signed زَهُّر
اليوم ماكو وادم
Signed زَهُّر
والله حبي دزيلي ماأقصر
Signed زَهُّر
عيوني
Signed زَهُّر
💌 وصلتك رسالة جديدة ⏱ وقت الرسالة: 2026/08/17 - 09:23:57 PM ---- حموتتتتتت ---- - تبرع لإستمرار عمل بوت صارحني 🎁
Signed زَهُّر
💌 وصلتك رسالة جديدة ⏱ وقت الرسالة: 2026/08/17 - 09:23:54 PM ---- زهره ---- - تبرع لإستمرار عمل بوت صارحني 🎁
Signed زَهُّر
منعيوني❣️
Signed زَهُّر
حُبي دزيلي أني أدزهن ألچ حتى تكمل الچذبه
Signed زَهُّر
Showing the 12 most recent of 44 posts we hold for @GD16k. 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.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
This channel appears in 57 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“زَهرة” (@GD16k), 15,030 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/GD16k.
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.