佳佳的小🏘️ pinned a photo

Channel
佳佳的小🏘️
@hdjk776
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,088subscribers
+783 since we began measuring on 24 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003937131762 |
|---|---|
| Type | Channel |
| Username | @hdjk776 |
| Created | Between 1 April 2026 and 19 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/hdjk776 |
Topic
Giveaways & airdrops — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 12:58 | 1,088 | -7 |
| 11 Sept 2026, 22:19 | 1,095 | -48 |
| 7 Sept 2026, 08:38 | 1,143 | -4,914 |
| 2 Sept 2026, 23:25 | 6,057 | -722 |
| 30 Aug 2026, 23:17 | 6,779 | +1,051 |
| 27 Aug 2026, 22:44 | 5,728 | +4,463 |
| 25 Aug 2026, 03:53 | 1,265 | +960 |
| 24 Aug 2026, 07:00 | 305 | no change |
| 24 Aug 2026, 06:45 | 305 | first reading |
Engagement
20 posts held, back to 19 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.
- ERR · 30 days
- 8.13%
- avg views ÷ 1,088 subscribers
- Avg views / post
- 88.5
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 5
- of 20 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 20 (19 August 2026 – 24 August 2026) |
| Views total | 354 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 24 Aug 2026, 07:00 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Recent posts
🎰 佳佳的夏日福利 📮 抽奖条件: 🎫 加入-杭州肯德基 🎫 加入-杭州全家桶菜单 🎫 加入-杭州肯德基工兵 🎫 加入-佳佳的小🏘️ 🎁 奖品内容: 半价p × 1 口令50 × 1 💡 活动说明: 本次活动由 #佳佳 @jiajia7798 独家赞助,优惠7日兑换,口令3日兑换 📅 开奖日期:(UTC+8) 2026年08月29日 20时00分00秒
12点开课啦哥哥们 头课还在 痛死我啦😭
Photo, posted without a caption
杭州御女阁出击报告模板: https://t.me/hangzhou_777 评分标准: 9分 【老师艺名】:佳佳 【联系方式】:@jiajia7798 【老师芳邻】:18 【验证留名】:Alexander 【出击时间】:8月22日 【大概位置】:上城区 【出击水费】:竞拍pp 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ④ 毒龙 【人照相似】:真人照片,傻白甜颜,本人比照片好看! 【身高身材】:160左右,无符文,全身白净,身材匀称 【凶器罩杯】:B罩,一手掌握,手感柔软 【湿度紧度】:外褐内粉!毛量较少!妹妹很嫩!内部温暖!包裹十足 【环境细节】:复式loft公寓!进出方便!开车停车方便! 【个人卫生】:有漱口水一次性浴巾事前有清洗 【时间管理】:开课准时!排课宽松! 【服务总结】:暑期工嫩妹!服务不太会做!态度很好!主要是嫩!过程无机车!嫩妹三件套 【…
Sticker, posted without a caption
今天下班啦哥哥们 可以预约明天啦
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178731601165 🎰 杭州修车协会福利【佳佳】 ⚠️ 抽奖说明: 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等,一律视为无效发言,不计入统计!请用心交流。 开奖如果不在群内,一律视为自动放弃,奖品将会回到奖池继续抽奖活动最终解释权归本群管理团队所有。 中奖的人员核实元宝数量,开奖即查,达到200扣除后再联系老师约定约时间(在抽奖期间提交过本群老师原价出击报告可以不扣除直接兑奖),元宝不够奖品作废回到兑换区供其他狼友兑换 24小时内预约时间,3天内出击,过时自动作废 中奖需本人出击,转让需经过老师同意并与管理协商,不得私下买卖,出现买卖双方都将被踢出群里!出击完成后提交报告(提交报告额外奖励元宝)如若不提交,将永久拉黑! 老师:@jiajia7798 喜欢的再抽,抽中的请珍惜。愿每一次抽奖,都是一次心动的选择。 💁 参与情况:35达标 / 42报名 🔋 人品加成:…
杭州御女阁出击报告模板: https://t.me/hangzhou_777 评分标准: 9.5分,女友系嫩妹 【老师艺名】:#佳佳 【联系方式】:@jiajia7798 【老师芳邻】:18 【验证留名】:华佗 【出击时间】:8.22 【大概位置】:上城 【出击水费】:800p 【高端服务】:有的打✅ ① 舌吻 ✅✅(大量管饱,主动索吻) ② 69舔逼 ✅✅(褐色小蝴蝶,出水量超大) ③ 情绪价值 ✅✅(夯!沉浸式体验与女友缠绵) ④ 毒龙 【人照相似】:真人比照片好看,照片8分,真人9.5,没穿搭光溜溜的躲在被窝里,小脚丫车厘子美甲看起来很有食欲 【身高身材】:160左右,身材很棒,学过舞蹈,白皮有弹性,pp超弹。 【凶器罩杯】:胸B,乳头挺拔,小枣一样,把玩手感很棒。摸一下就立起来了 【湿度紧度】:户型小蝴蝶,浅褐色,紧度适中,但是出水量超大,流了一手,拔萝卜过程非常润滑,通道又…
12点开课 头课还在
https://t.me/kdjqjt
Posted without readable text
Showing the 12 most recent of 20 posts we hold for @hdjk776. 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
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“佳佳的小🏘️” (@hdjk776), 1,088 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/hdjk776.
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.