独家五年医疗消费记录已恢复 全天24小时秒 文档3u图版3u @xintyyyyybot @xintyyyyybot @xintyyyyybot
👍2
Signed 心疼个户官方客服

Channel
@cintyyyyy
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
8,923subscribers
+99 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003537341990 |
|---|---|
| Type | Channel |
| Username | @cintyyyyy |
| Description | Dear Channel Administrators, Members, and Telegram Team: This channel strictly prohibits posting any information in any areas that violates legal regulations or Telegram's policies, including content related to politics, violence, or infringement of othe |
| Created | Between 1 December 2025 and 15 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/cintyyyyy |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 14:37 | 8,923 | +10 |
| 11 Nov 2026, 10:10 | 8,913 | +10 |
| 7 Nov 2026, 07:19 | 8,903 | +6 |
| 1 Nov 2026, 07:06 | 8,897 | -3 |
| 28 Oct 2026, 20:49 | 8,900 | +5 |
| 25 Oct 2026, 13:28 | 8,895 | -2 |
| 22 Oct 2026, 07:10 | 8,897 | +1 |
| 15 Oct 2026, 11:29 | 8,896 | +1 |
| 12 Oct 2026, 18:31 | 8,895 | +4 |
| 29 Sept 2026, 11:59 | 8,891 | +1 |
| 15 Sept 2026, 13:16 | 8,890 | -1 |
| 12 Sept 2026, 07:00 | 8,891 | -3 |
| 8 Sept 2026, 09:38 | 8,894 | +21 |
| 3 Sept 2026, 06:13 | 8,873 | +17 |
| 30 Aug 2026, 15:54 | 8,856 | -6 |
| 27 Aug 2026, 20:05 | 8,862 | -2 |
| 24 Aug 2026, 12:09 | 8,864 | +8 |
| 20 Aug 2026, 19:12 | 8,856 | +14 |
| 17 Aug 2026, 13:38 | 8,842 | +12 |
| 14 Aug 2026, 07:13 | 8,830 | first reading |
38 posts held, back to 15 April 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 60 pages of 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.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 38 (15 April 2026 – 25 October 2026) |
| Views total | 477 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 14:12 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.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
46 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 54.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 54.3% | |
| 👍 | 7 | 15.2% | |
| 😱 | 7 | 15.2% | |
| 🤣 | 7 | 15.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 19 of the 38 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 15 April 2026 to 25 October 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.
Telegram’s own ‘edited’ marker: 1 of 1 post held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
独家五年医疗消费记录已恢复 全天24小时秒 文档3u图版3u @xintyyyyybot @xintyyyyybot @xintyyyyybot
👍2
Signed 心疼个户官方客服
房屋抵押查封状态 1️⃣5️⃣ 提供房屋产权号查询 部分地区需要详细地址 当天隔天回
👍2
Signed 心疼个户官方客服
强登12306 2️⃣0️⃣ 姓名身份证手机号+大头报单 出近半年12306高铁火车订票记录 无遗漏 包含未出行订票信息 以及同行人
👍3
Signed 心疼个户官方客服
三网通话记录开 一月 2️⃣5️⃣0️⃣ 三月 5️⃣5️⃣0️⃣ 六月 7️⃣5️⃣1️⃣ 一年 1️⃣1️⃣0️⃣0️⃣ 两年 1️⃣3️⃣0️⃣0️⃣ 移动联通电信 三大运营商直出 无遗漏 当天隔天出
❤1
Signed 心疼个户官方客服
淘宝闪购 1️⃣2️⃣0️⃣ 手机号报单 出最新五条地址 一条也收费 隔天回单
Signed 心疼个户官方客服
犯罪服刑记录开 4️⃣0️⃣ 已测试稳定回单 当天隔天回 空给图收费 独家源头收单 代理拿价
Signed 心疼个户官方客服
名下资产查询 4️⃣5️⃣0️⃣ 名下银行卡账户余额 名下支付宝微信账户余额 名下房 名下车辆 民政婚姻 名下保险 证券(系统反馈多少给多少) 一周左右回 姓名身份证报单 敏感不要 北京上海不要 源头出单 批量价优
Signed 心疼个户官方客服
高德打车 5️⃣0️⃣ 报单提供 名字+身份证+手机号+大头 出单内容点击板子查看 人在就秒
Signed 心疼个户官方客服
公安地址5️⃣0️⃣1-2天左右回单,报单提供二要素,概率送同户人信息,同户人不保漏,空不收费 现住地址不是库,同户人有遗漏是概率送,可能会空。 地址如果出到现住地和户籍地都是一个地方,表述不一样的也正常计费,例如户籍地址是“1栋12室”,出的现住地是“1栋12房”,一个字的差别也正常计费,当天隔天回单。
Signed 心疼个户官方客服
公网水电地址(正规水电系统出品)3️⃣0️⃣ 一个身份证下面多户 第一户3️⃣0️⃣第二户2️⃣5️⃣ 只要1户的话备注 只要1户 默认出全部 提供 手机号 身份证均可报单 当天隔天回
Signed 心疼个户官方客服
1.美团最新地址 1️⃣8️⃣0️⃣ 半年内最新十条 一条也收费 不满5条 收一半 文字回单 真美团随时埋雷打假!!! 独家业务,已测试,真正的美团 (好业务永远是贵的 垃圾便宜的永远找不到人 找人必备强推荐) 提供:手机号报单 2. 美团饿了么闪购3️⃣5️⃣0️⃣ 当天回单 不保漏 私聊拿模板 带订单编号 下单人手机号 收货人手机号 收货地址 商家名称 商家地址 商家id 商品详情 身份证 电话报单 好渠道不常有 需要的抓紧来
❤1
Signed 心疼个户官方客服
业务名称:出入境+名下护照明细 5️⃣ 提供资料:姓名 身份证 大头 查询结果:出入境明细 出单时间:当天
Signed 心疼个户官方客服
Showing the 12 most recent of 38 posts we hold for @cintyyyyy. 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.
@cintyyyyy edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 4 posts on @cintyyyyy as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“心疼源头查档 模板频道” (@cintyyyyy), 8,923 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/cintyyyyy.
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.