Telegram RegisterThe public register of Telegram

Channel

蛋蛋的小屋

@wgtdhe

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1,378subscribers

+14 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002713664143
TypeChannel
Username@wgtdhe
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/wgtdhe

Growth

1,3641,3781,37110 August 2026 — 1,364 subscribers11 August 2026 — 1,366 subscribers14 August 2026 — 1,378 subscribers10 August 202614 August 2026
3 measurements spanning 4 days, net +14. 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,362–1,380 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 17:381,378+12
11 Aug 2026, 01:511,366+2
10 Aug 2026, 06:011,364first reading

Engagement

17 posts held, back to 28 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
37.2%
avg views ÷ 1,378 subscribers
Avg views / post
513
17 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
17
of 17 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. It is computed over the 1 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held17 (28 July 20264 August 2026)
Views total8,726
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 06:01 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.

What this channel posts

Video runtime
3s
Average length
3s

Measured directly from 1 video 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.

Recent posts

2 Aug 2026, 08:50 UTC492 viewsread 10 August 2026

成都星辰楼凤修车群专用报告模板 基础信息 【妹子花名】:#蛋蛋 【妹子车牌】:@Yxcdmu0 【验证留名】:废废弗弗 【验证时间】:8.2 【所在位置】:石羊场 【修车水费】:6P 9PP 【是否代聊】:代聊 硬件🤤🤤 【身高体重】:身高168cm,体重110多斤,微胖型,小臂一点纹身,正常肤色,皮肤光滑。 【妹子年龄】:22 【湿度紧度昆感】:毛量多,湿润,敏感 。 【人照相似】:8分 【颜值打分】:8分(6分及格,8分班花,9分 小网红,碰见想要微信那种) 【凶器罩杯】:胸天然E,一手无法掌握。乳晕大,乳头小,颜色正常褐色。 软件❤️❤️ 【环境卫生】:出入方便,房间干净 【服务内容】:陪洗,大蟒蛇、口、做 【机车行为😓】:无 综合 【优点缺点】:优点: 四川本土巨乳嫩妹,胸真大超级大,又大又软,巨乳巨臀爱好者福音。态度超级好,主动大蟒蛇,吃饱管够,人不精神,沟通交流都挺好的。 缺点: 微胖,

2 Aug 2026, 03:24 UTC452 viewsread 10 August 2026

【楼凤阁专用模板】 【妹子花名】:蛋蛋 【联系老师】:@Yxcdmu0 【验证留名】:lingqin 【验证时间】:2026.7.30 【所在位置】:保利 【修车水费】:600 【是否代聊】:是 【身高身材】:170 【妹子年龄】:24左右 【湿度紧度】:有包裹感但不强 【颜值相似】:9 【凶器罩杯】:E 【环境卫生】:8 【服务内容】:口,洗浴,爱爱,kiss 【机车行为】:无 【优点缺点】:口技非常好 【性价比】: 8/满分10分; 【推荐程度】:8/满分10.0分; 评分标准 6分为及格,7分为良品(考虑价格可以看一看),8分(值得价格并且建议体验),9分(实为该价位中少见的精品),10分(极品) 【个人发挥】:代哥给地址后上楼,老师穿着女仆装在门后等我,老师有点微胖,交完课费就开始洗浴,老师很健谈,但有点太实诚了,老师帮我口的时候很爽,口技很棒,老师是不易高潮体质,有能力的兄弟可以去试试 https://t.

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

Citation-graph rank — 558,942 of 1,350,102entries 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.

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

“蛋蛋的小屋” (@wgtdhe), 1,378 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/wgtdhe.

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.