Telegram RegisterThe public register of Telegram
Telegram profile photo for 德焕朋友圈

Channel

德焕朋友圈

@dehuanbjbudi

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

1,742subscribers

+43 since we began measuring on 21 August 2026

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

Register entry

Telegram ID-1002106825549
TypeChannel
Username@dehuanbjbudi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live18 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/dehuanbjbudi

Topic

Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

1,6991,7461,722.521 August 2026 — 1,699 subscribers21 August 2026 — 1,699 subscribers23 August 2026 — 1,707 subscribers25 August 2026 — 1,724 subscribers29 August 2026 — 1,731 subscribers1 September 2026 — 1,745 subscribers14 September 2026 — 1,746 subscribers18 September 2026 — 1,742 subscribers1,74221 August 202618 September 2026
8 measurements spanning 28 days, net +43. 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 1,692–1,753 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 19:551,742-4
14 Sept 2026, 04:151,746+1
1 Sept 2026, 12:131,745+14
29 Aug 2026, 01:531,731+7
25 Aug 2026, 20:071,724+17
23 Aug 2026, 04:441,707+8
21 Aug 2026, 20:001,699no change
21 Aug 2026, 19:451,699first reading

Engagement

15 posts held, back to 8 May 2026the 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
11.5%
avg views ÷ 1,742 subscribers
Avg views / post
201
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 15 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 21 August 2026
Posts held15 (8 May 202621 August 2026)
Views total201
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Aug 2026, 20: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.

Reaction mix

11 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 81.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
981.8%
👍218.2%

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 6 of the 15 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 8 May 2026 to 21 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.

Recent posts

15 Jul 2026, 06:35 UTC≈2,320 views3 reactionsread 21 August 2026

上海美少女报告模板 【位置艺名】:德焕 【联系方式】 @Dehuanya 【喝茶留名】:美少女异域美食家 【喝茶时间】:7.15 【喝茶价格】:1900PP 【芳龄身高】:成都女孩身高,二十多岁 【罩杯手感】:E杯挺括,真实不虚 【服务内容】:口做 【优点缺点】:优点很多,慢慢道来 【体验细节】:本美食家对于异国美女向来兴趣满满,德焕是美少女唯一一个越南美女,在这个炎热的午后终于得见。 抵达市中老小区,进入虚掩的门,德焕就在后面羞涩的笑着,短发蘑菇头,娃娃脸,眼睛溜圆,看上去很像初高中班级里评选的最可爱的那个女孩子,但是惊异的是一对E乳呼之欲出,圆润挺拔,所谓童颜巨乳是也。虽然个子不高,但是前凸后翘的玲珑身也着实令人赞叹。 洗毕入榻,摸上去肤若凝脂,不禁说到:越南人都是这么皮肤好吗,腹部无赘肉,但是臀又是如此饱满坚实,尤其是蜜穴,汁水四溢,揉上去噗噗作响,德焕的口技也是极好的,舌弹跳舔舐,全方位照顾每一个敏感点。实在受不了了戴

2👍1

10 Jul 2026, 12:54 UTC≈2,610 views2 reactionsread 21 August 2026
Photo

德焕(越南女孩) 艺名:德焕 产地:胡志明市 年龄:03 身高:160 胸围:D 体重:45kg 阿焕,上海首开,超白级牛奶肌,一线天,超级粉嫩,是超粉色 ,前凸后翘 腰很细 会三国语言 越南 中文 英语 证件快到期要回国,纯纯的短开, 驾照免费 驾越南免费 上课内容 裸吹,陪浴,🐍吻,69,🐻推,调情,情趣内衣,制服诱惑,丝袜,高跟鞋👠 课费 1200/p(50分)1900/pp(80分) 禁止:🈚️套,撞机,变态,桩机(1米9,200斤肉山不接) 联系方式 @Dehuanya

2

8 May 2026, 15:21 UTC≈4,450 views4 reactionsread 21 August 2026
Forwarded from @hxshyxPhoto

🌸艺名: #德焕 💃年龄: 03身高: 160体重: 45🐻:D 📍位置: #静安 💸价格: 1200p/50min 1900pp/90min 📱联系老师: @Dehuanya ✈️老师频道: https://t.me/dehuanbjbudi 🏷标签: 裸吹#舌吻69#陪浴#胸推#调情#丝袜制服 韩信上海优选榜:@hxshyxn 上海大圈外围:https://t.me/ccxkshww 联系老师请说:韩信优选榜看到推荐的: 上海韩信雷榜:https://t.me/hxshlb

3👍1

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — 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.

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

“德焕朋友圈” (@dehuanbjbudi), 1,742 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dehuanbjbudi.

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.