Telegram RegisterThe public register of Telegram
Telegram profile photo for 远洋平价查档批发 业务通知频道

Channel

远洋平价查档批发 业务通知频道

@YYCD_2

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

15subscribers

+6 since we began measuring on 20 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004445721498
TypeChannel
Username@YYCD_2
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 October 2026
Last confirmed live29 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/YYCD_2

Growth

9151220 October 2026 — 9 subscribers20 October 2026 — 9 subscribers21 October 2026 — 10 subscribers29 October 2026 — 15 subscribers20 October 202629 October 2026
4 measurements spanning 9 days, net +6. 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 8–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Oct 2026, 04:4015+5
21 Oct 2026, 17:2010+1
20 Oct 2026, 16:229no change
20 Oct 2026, 15:479first reading

Engagement

20 posts held, back to 15 October 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
113.0%
avg views ÷ 15 subscribers
Avg views / post
16.9
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 20 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 20 October 2026
Posts held20 (15 October 2026 – 20 October 2026)
Views total339
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Oct 2026, 16:22 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

20 Oct 2026, 11:34 UTC13 viewsread 20 October 2026
Photo

房管局房产回完 继续上 首套 ❤️❤️❤️ 后续每套 ❤️❤️ 带抵押状态 查封状态 支持埋雷测试 保售后 默认出全国范围 不可排除 不可指定 房产 商铺 车位 宅基地 有什么出什么 报单带名字身份证 源头出单 批量来谈 注:目前的房产局房产 不带详细门牌号 其他的什么都有 房屋产权号 地址 抵押状态 查封状态 新单工作日每天都发车 2-3工作日 很稳定

20 Oct 2026, 06:17 UTC15 viewsread 20 October 2026

无盲开卡流水。❤️❤️❤️ 晚上发车 周五回 同行代理 来拿优势

19 Oct 2026, 05:52 UTC38 viewsread 20 October 2026
Photo

远洋平价查档-综合最强!押金100000U+ 每日必需且便宜的特价小产品 小 关 联 ❤️❤️ 出 入 境 ❤️❤️ 单头全户 ❤️❤️ 学籍学历 ❤️❤️ 民政婚姻 ❤️❤️ 医保单位 ❤️❤️ 医疗记录 ❤️❤️ 常用地址 ❤️❤️ 网警地址 ❤️❤️ 美团P图 ❤️❤️ 淘宝地址 ❤️❤️ 水电地址 ❤️❤️ 宽带地址 ❤️❤️ 京东地址 ❤️❤️ 刑侦地址 ❤️❤️ 邮政多地址 ❤️❤️ 拼多多地址 ❤️❤️ 快递7合1地址 ❤️❤️ 高速记录 ❤️❤️ 短信记录 ❤️❤️ 历史购物记录 ❤️❤️ 移动名下号码 ❤️❤️ 抖音快手微博评论 ❤️❤️ 名下抖音快手小红书 ❤️❤️

18 Oct 2026, 07:30 UTC34 viewsread 20 October 2026

无盲经侦开卡快线 ❤️❤️❤️ 只要个户开卡 无上限 系统有多少给多少 保真不包漏 出单有记录就收费 同行 盘口批量拿优势 晚上发车 1-2回 发车包交付渠道

17 Oct 2026, 16:05 UTC34 viewsread 20 October 2026
Photo

置顶消息可直接进入业务目录 每日最新稳定可交付业务及价格 需要什么自主查看后联系我们下单 尽量减少无效沟通 模版没有的就代表全网没开 不用继续问 只要开的业务都会更新在模版频道 其次不光要对比价格还看看回单真实度以及是否稳定 以免被骗或伤下面代理 希望在查档的道路上一起成长 共同进步 祝所有客户2026年龙马精神 财源广进💰 个人信息类目 小 关 联 个人户籍 全家户籍 婚姻记录 学籍学历 医保记录 医疗记录 名下资产 大数据征信 名下手机号 个人名下卡 个人名下房 个人所得税 强登12306 人行征信报告 房屋抵押状态 法院诉讼+判决 名下护照+出入境 公司信息类目 公司档案 公司发票 营业执照 公司名下卡 公户银行流水 公司名下卡余额 车辆信息类目…

17 Oct 2026, 14:35 UTC17 viewsread 20 October 2026

五年飞火 ❤️❤️❤️ 当天隔天回 敏感扣单 同行代理价优

17 Oct 2026, 11:59 UTC18 viewsread 20 October 2026
Photo

名下资产回完 稳定 继续上 目前最好最全的法院渠道 基金股票保险也可以出 名下资产 法院直出 ❤️❤️❤️ 1. 名下全部银行卡卡号 + 账户余额(剔除:不活跃账户、睡眠卡、已注销卡) 2. 名下全部实名微信账户余额 3. 名下全部实名支付宝账户余额 4. 名下股票、证券、保险资产信息 私信看版 敏感收费不给单 1-3回 保真不包漏

17 Oct 2026, 05:21 UTC14 viewsread 20 October 2026

无盲快速经侦开卡专线 ❤️❤️❤️ 只要个户开卡 无上限 系统有多少给多少 保真不包漏 出单有记录就收费 同行 盘口批量拿优势 周天发车 1-2回 发车包交付渠道

16 Oct 2026, 12:31 UTC15 viewsread 20 October 2026
Photo

柜台包遗漏流水回完 没来的再等等 不同银行回单时间不一样 2026稳定至今不翻车路线 嘎嘎稳定 新单周末继续发车 柜台个户公户开卡流水 包遗漏流水 个人开卡 ❤️❤️❤️ 公司开卡 ❤️❤️❤️ 民生|农业|交通|平安 招商|工商|建设|中信|兴业 已稳定半年老线路 空不收费 其他有任何数据都收费 国企 上市公司不要 其他都要 小贷也可以 敏感扣单 包遗漏渠道 对单子有任何疑问都可复查 比此渠道出的多 都无理由退款 周末晚上12点发车 3-7个工作日左右回

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

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

“远洋平价查档批发 业务通知频道” (@YYCD_2), 15 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/YYCD_2.

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.