Telegram RegisterThe public register of Telegram
Telegram profile photo for 灰度肯尼亚支付

Supergroup

灰度肯尼亚支付

@hddb_KE

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

4,546members

-340 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002048335571
TypeSupergroup
Username@hddb_KE
Description灰度官网: www.huidu.io 交流社群: @huidu_shequ 资源社群: @hddbdaqun 灰度公群: @hddbgongqun 供需信息: @hddbgongxu 公告频道: @hddbgg 曝光频道: @hddb_bg 担保规则: @hddb_guize 安全防范: @hddbaq 灰度Bot: @huidubot 担保客服: @huiducn 对接联系: @HDdian
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live2 September 2026
Measurements held11
On Telegramt.me/hddb_KE

Growth

4,5464,8864,7167 August 2026 — 4,886 members7 August 2026 — 4,880 members11 August 2026 — 4,841 members14 August 2026 — 4,808 members17 August 2026 — 4,768 members20 August 2026 — 4,743 members24 August 2026 — 4,675 members27 August 2026 — 4,634 members30 August 2026 — 4,561 members2 September 2026 — 4,546 members2 September 2026 — 4,546 members7 August 20262 September 2026
11 measurements spanning 27 days, net -340. 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 4,495–4,937 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
2 Sept 2026, 23:394,546no change
2 Sept 2026, 18:424,546-15
30 Aug 2026, 12:354,561-73
27 Aug 2026, 05:114,634-41
24 Aug 2026, 06:084,675-68
20 Aug 2026, 14:534,743-25
17 Aug 2026, 20:374,768-40
14 Aug 2026, 18:294,808-33
11 Aug 2026, 07:424,841-39
7 Aug 2026, 23:574,880-6
7 Aug 2026, 06:514,886first 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.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“灰度肯尼亚支付” (@hddb_KE), 4,546 members as measured 2 September 2026. Telegram Register, tgregister.com/channel/hddb_KE.

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.