Telegram RegisterThe public register of Telegram

Channel

Telegram User's

@Hamddd

On this record: Growth · Engagement · Posts · Citations · Cite this entry

11subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001593401345
TypeChannel
Username@Hamddd
DescriptionHey everyone : @zcbot 💙.
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/Hamddd

Growth

117 August 2026 — 11 subscribers12 August 2026 — 11 subscribers7 August 202612 August 2026
2 measurements spanning 5 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:1511no change
7 Aug 2026, 08:2811first reading

Engagement

20 posts held, back to 16 September 2024 — 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 pageof 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 31 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

Showing the 12 most recent of 20 posts we hold for @Hamddd. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

MuStaFa
@suuffe · 1132 postsA
@aaaaaaa · 201 postTOS - @hacktivc
@caaca · 211 postايليا
@HJHHH · 61 postFuck ²
@Jurdn · 2031 post*_*
@k_eko · 3821 post𝗞𝗮𝗿𝗮𝗺 𝗦𝘁𝗼𝗿𝗲
@KNKKK · 3061 postشتبوستر - Skay
@lslll · 6611 post@mmmmm
@mmmmm · 3881 postشِغَف ْ | shaghaf
@n1nnn · 277,4351 post愿许秋天知你意
@qiutian · 3661 postRo
@rooro · 221 postChannel - 88
@rrlrr · 2111 postb.cc 博彩朋友圈@uuuuuu靓号5u6u7u
@uuuuuu · 3761 post@vip54
@vip54 · 171 post少女镇防失联🤣
@xoxoo · 164,9051 postادوات بايثون • Python Tools
@yy_100k · 159,7911 postملصقات تمبلر كروبات دردشه
@zz2zz · 150,3771 postخلفيات اشعار صور بنات رمزيات
@zzuzz · 873,0891 post

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.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Telegram User's” (@Hamddd), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Hamddd.

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.