Channel
@Dgyummy005
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,869subscribers
+63 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003835953464 |
|---|---|
| Type | Channel |
| Username | @Dgyummy005 |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Dgyummy005 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:13 | 1,869 | +62 |
| 8 Aug 2026, 04:28 | 1,807 | +1 |
| 8 Aug 2026, 01:02 | 1,806 | first reading |
14 posts held, back to 11 July 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 pageof Telegram’s post history, 20 posts per page.
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. It is computed over the 9 of 10 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 14 (11 July 2026 – 4 August 2026) |
| Views total | 32,280 |
| Reactions total | 54 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:02 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.
Measured directly from 9 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.
80 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 61.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 49 | 61.3% | |
| 💩 | 15 | 18.8% | |
| 🤡 | 6 | 7.50% | |
| 👍 | 4 | 5.00% | |
| 👏 | 2 | 2.50% | |
| 🤔 | 2 | 2.50% | |
| 🤯 | 2 | 2.50% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 14 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 80reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 11 July 2026 to 4 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
【S】 #东城 安怡 @anyi988 6p 19s，160cm，45kg，C+，白皮，🚬，无纹身。自聊，川妹妹，人照接近，大眼灵动活泼可爱邻家小妹妹，举止得体，笑脸迎客，挺乖巧的印象分不错。皮肤白皙嫩滑，肉嘟嘟的婴儿肥，真是卡哇伊🤏 👍👍瘦底大胸，有点小肚肚没影响，身材跟puyou接近，熊还要大一丢丢，雪白的胸脯手感很好，🐻奴必冲 👍👍冷白皮，有点婴儿肥更可爱辣，软糯糯的pp手感一绝，几乎是煮啵抓过手感最好的pp 👍👍ok紧，润，配合，后入会塌腰，反馈很赞，下下有回声，娇滴滴的喘声相当动听 🆗有🐍和69，半个小蟒蛇，69挺敏感，会撒娇求饶。 👎口的时间有点短，69后可能不给🐍 她那软软糯糯的手感、如雪粉嫩的胸脯、绵软柔和的性格，突然让煮啵想起好多故人😭
❤2👍1
顶级工兵又把我撩的心乱如麻 真是个fvv🤡
不更实在是因为么得下吊 勿念（准备更几个老频道的糊弄一下🤡）
🤡6❤1
【B+】 #南城 清瑶 @qingSyao 6p 18s，160cm，圆圆的C+，黄皮，好像没纹身，弗兰人？自聊，刚出道叫伊崽，人照6.5分左右，仙气滤镜略狠，真人与视频相近，中下颜吧，比较幼态的脸，妆日常让兄弟们吃花了，算是素颜，有点大头娃娃，话痨加随性的可爱型妹妹。 👍圆圆的C+，匈奴狂喜 👍👍超级大蟒🐍，会主动索吻，糊煮啵一脸口水， 👍👍口的深舔的认真，口活对蜻蜓点水般嫩妹带降维打击 👍紧、润、热辣滚烫，暴力女桩基，传教士还摁着煮啵的头啃，招架不住又是123的一天😭 完事还下楼请煮啵喝柠檬茶，不又双叒想起某位故人....潜力股吧，加强一下形象管理和房间整洁就更好辣
❤6🤯2
好爱 好想… 有没有这款老师😭
❤4🤔2
旧的有点好吃 最近应该不工了 备用频道 @DGyum06
❤2
【S+】 #松山湖 Coco @cz773355 7p 18s，167cm，47kg，D🐻，黄白皮，不抽烟，无纹身，湘妹子，自聊，喜欢小动物，喜欢打游戏，喜欢叫爸爸，喜欢...一个成熟的老师自是什么话题都能接住，仿佛你说的每一个爱好每一个细节每一个游戏都是她的心头好，还没脱衣服煮啵就开始沦陷了 👍👍👍终极进化后已是成熟竹竿胴体，笔直的细长腿，沿着A4腰往上扫是两颗硕大的棉花，三点还粉让人怎么忍，如此大自然的鬼斧神工，身材控已无脑冲 👍口得很认真，过程中一双媚眼摄人心魄，冷不防几下舌转龟头差点让我交代 👍馒头户型，柔韧极好，任盘耐桩，疯狂女骑，持续的浪叫输出，煮啵被干的有点迷糊，留点想象空间吧 🆗无69，懒得问了，下回再吃 👎极度难约，煮啵几度破防😭 实在很难想象这张甜度爆表的娃娃脸、娴熟的服务、激烈浓厚的性爱和课后天真烂漫的聊天搭在一起，这就是理想中我的反差女友吗 煮啵进门就后悔了，后悔没有早…
❤10
【A+】 #南城 晶晶 @jjncdddj 6p 18s，158cm，44kg，B+，黄皮，🚬，0纹身。代聊，广西表妹。非常瘦的妹妹，很小一只，人照基本一致，甚至滤镜都懒得加，颜值略带表妹村味嘴边有圈绒毛（哈哈哈哈），手脚都有美甲首饰又拉回点精致感，刚出社会的模样，不算活泼但挺听话，进门会笑，态度不错，0鸡味，蹑手蹑脚的服务还有点可爱。 👍算得上瘦底大波，排骨之上挂着圆润大B，0赘肉🐒，皮肤嫩滑，屁股也有肉，嫩嫩嫩的小萝莉 👍👍有69，嫩、紧、润、敏感、反馈足，让人上头的紧润嘟感 🆗刚下海的白切🐔，没有流程概念，但耐心还不错，可以手把手教学，服务控需慎重，适合自助餐选手 🆗🐍有点拘谨，需要强硬点 她脱下裙子的瞬间我的侵略性完全爆发了，就这样123又321，直到她在强忍叫床中突然喊了声“好舒服”，彻底治愈了煮啵连吃几坨💩的伤疤 😭😭东城小沐沐南城分沐，就是颜值和🐍有差距，又想起故人了
❤2
疑似低配小沐沐🥰
❤1👏1
【S-】 #南城 小希 @xiaoxi466 8p 19s，167cm，51kg，B杯，人照差不多，挺可爱的，忘哪里人，中介代聊，以前叫洋洋，在7p和8p间反复横跳，有点呆，高个乖乖学生妹风格 👍👍真人真照，高颜，白皮，长腿，偏瘦，颜控、身材控可冲 🆗服务约等于无，不知道现在学会了没 👎嘟的反馈一般 👎可以亲亲，无🐍无69 去有点久了，课表改了无数次，7的时候硬件很顶，8的话体验跟价格...
💩8❤6
【B+】 #南城 念美 @aiaia8686 6p 22s左右，160cm，46kg，浑圆B+，人照7.5，脸上卡粉🤡，湖南人，自聊叼毛，线上会和客人聊天挺有趣，劳模型老师，🈚️🐍🈶69，一身秒人本领，耐桩会摇，水超级多，一顿猛捅后从🦋流到屁股整片三角区都是汪洋，噗呲水声相当悦耳，搭配上乳摇碰撞声和激烈叫🛏声，彷如性爱交响乐大师😋 新闻又开始播报新冠，养猪少女闪现回归，今夕是何年？ 翻出来1.0频道的旧作，我也不知道现在长啥样，韩老魔说还是很多水，煮啵便放心了😃
❤5👍1
我💗东城
💩7❤4👍2
Showing the 12 most recent of 14 posts we hold for @Dgyummy005. 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.
Citation-graph rank — 55,058 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 2 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“爱吃好吃的 5.0” (@Dgyummy005), 1,869 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Dgyummy005.
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.