【寻欢地点】:许昌(可上门) 【信息来源】:亲身体验 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱、SM 【妹妹数量】:1 【环境设备】:酒店,公寓 【营业时间】:指定时间 【价格一览】:700/P 【安全评估】:满分95 【服务星级】:★★★★★ 【重点推荐】:S身材,很棒

Channel
河南地区品茶🍵 楼凤外围资源
@Tddtdi
On this record: Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry
1,017subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001254165671 |
|---|---|
| Type | Channel |
| Username | @Tddtdi |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/Tddtdi |
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 11:04 | 1,017 | -2 |
| 23 Aug 2026, 12:38 | 1,019 | +2 |
| 19 Aug 2026, 16:33 | 1,017 | -3 |
| 16 Aug 2026, 22:17 | 1,020 | -5 |
| 13 Aug 2026, 23:25 | 1,025 | -2 |
| 10 Aug 2026, 20:46 | 1,027 | -2 |
| 7 Aug 2026, 17:03 | 1,029 | -1 |
| 7 Aug 2026, 01:31 | 1,030 | first reading |
Engagement
9 posts held, back to 14 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 · 30 days
- 5.93%
- avg views ÷ 1,017 subscribers
- Avg views / post
- 60.3
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 9 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 6 August 2026 |
|---|---|
| Posts held | 9 (14 July 2026 – 6 August 2026) |
| Views total | 362 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 01:31 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
全国各地资源 下面有对应的城市 🔞🔞🔞👇👇👇 https://t.me/+lrGqjfXhlJ8zNDJl
【寻欢地点】:河南 郑州 管城 【信息来源】:亲身体验 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱、 【妹妹数量】:1 【环境设备】:干净卫生 【营业时间】:12-12 【价格一览】:400单次 【安全评估】:评分,满分100。 【服务星级】:★★★★★(最高5星)应适当评价质量 【重点推荐】:最值得推荐的地方以供参考
【寻欢地点】:河南省郑州市金水区马庄小区 【信息来源】:狼友推荐、论坛、亲身体验 【服务项目】:鸳鸯浴,波推,臀推,69 ,舌吻,啪啪,口爆,丝袜调情 【妹妹数量】:1 【环境设备】:小区住宅 【营业时间】:下午2点 【价格一览】:500全套 【安全评估】:安全 【服务星级】:★★★★★
点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 点击解锁妹子的联系方式 有任何问题可以私信客服👉 @ZZXDHY_bot
【寻欢地点】: 郑州金水区农业东路如意西路交叉路口 【信息来源】:亲身体验 【服务项目】:鸳鸯 胸推,69,冰火,爱爱,制服 口爆 【妹妹数量】:1 【环境设备】:安全干净 【营业时间】:12点到2点 【价格一览】:600 【安全评估】:90 【服务星级】:★★★★ 【重点推荐】: 口爆 69
【寻欢地点】:郑州 【信息来源】:亲身体验 【服务项目】:鸳鸯浴,漫游,胸推,69式,冰火,口活,爱爱 【妹妹数量】:1 【环境设备】:安全可靠 【营业时间】:自己约 【价格一览】:全套八百 【安全评估】:98 【服务星级】:★★★★★ 【重点推荐】:身材好水多,服务好不机车
【寻欢地点】:郑州管城回族区 【信息来源】:亲身体验 【服务项目】:鸳鸯浴,漫游,胸推,冰火,制服,爱爱 【妹妹数量】:1 【环境设备】:小区 【营业时间】:晚上8点 【价格一览】:500 【安全评估】:100分 【服务星级】:★★★★★ 【重点推荐】:服务好
【寻欢地点】:郑州市金水区花园路金元公寓 【信息来源】:亲身体验 【服务项目】:69式,调情 丝袜诱惑 口爆、 鸳鸯戏水,深喉 【妹妹数量】:1 【环境设备】:干净卫生 【营业时间】:自己约 【价格一览】:688一次 【安全评估】:安全 【服务星级】:★★★★★ 【重点推荐】:极品69式
Showing the 9 most recent of 9 posts we hold for @Tddtdi. 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 — 73,146 of 1,604,251entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“河南地区品茶🍵 楼凤外围资源” (@Tddtdi), 1,017 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/Tddtdi.
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.