Telegram RegisterThe public register of Telegram
Telegram profile photo for 富城业务中心

Channel

富城业务中心

@fczxyw

On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry

4,746subscribers

-4,536 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002039656753
TypeChannel
Username@fczxyw
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live29 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/fczxyw

Growth

4,7469,2827,01415 August 2026 — 9,282 subscribers16 August 2026 — 8,890 subscribers19 August 2026 — 7,908 subscribers23 August 2026 — 6,590 subscribers26 August 2026 — 5,704 subscribers29 August 2026 — 4,746 subscribers15 August 202629 August 2026
6 measurements spanning 14 days, net -4,536. 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 4,066–9,962 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 20:134,746-958
26 Aug 2026, 10:055,704-886
23 Aug 2026, 17:546,590-1,318
19 Aug 2026, 22:347,908-982
16 Aug 2026, 17:148,890-392
15 Aug 2026, 19:309,282first reading

Engagement

22 posts held, back to 8 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 7 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.87%
avg views ÷ 4,746 subscribers
Avg views / post
41.3
7 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
9
of 22 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 7 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 19 August 2026
Posts held22 (8 July 202619 August 2026)
Views total289
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 20:21 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

16 Aug 2026, 17:55 UTCviews —

富城业务中心 pinned «查檔類基础业务 婚姻帶歷史6U 單頭假地4U 常規法人3U 高級法人6U 全頭全戶22U 單頭全戶13U 身份證正反6U 抖反散單2U 三網名下號3U 七合一快遞20U 社保歷史記錄15U 出入境記錄10U 預留2U 《批量來聊》 破解卡反4U 《批量來聊》 剩菜卡反15U 條子卡反25U 醫保繳費記錄15U(可看繳費單位) 出入境8U 個人名下銀行卡40U 個人名下車25U 全國房產首套120U次套60U 公網微反一件套 40U 公網微反二件套130U 手機定位130U-180u …»

16 Aug 2026, 17:55 UTC30 viewsread 22 August 2026

查檔類基础业务 婚姻帶歷史6U 單頭假地4U 常規法人3U 高級法人6U 全頭全戶22U 單頭全戶13U 身份證正反6U 抖反散單2U 三網名下號3U 七合一快遞20U 社保歷史記錄15U 出入境記錄10U 預留2U 《批量來聊》 破解卡反4U 《批量來聊》 剩菜卡反15U 條子卡反25U 醫保繳費記錄15U(可看繳費單位) 出入境8U 個人名下銀行卡40U 個人名下車25U 全國房產首套120U次套60U 公網微反一件套 40U 公網微反二件套130U 手機定位130U-180u ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

16 Aug 2026, 17:52 UTC28 viewsread 22 August 2026

车轨5+1 😃😄😄😆 提供车牌号 出最新一个月内100条行驶记录 注意:有的车没有车图 不满100条有记录出单即收费 最近一个月没记录就往前推一个月 保真不保漏 ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

15 Aug 2026, 08:32 UTC39 views0 reactionsread 22 August 2026

银行流水 8月16日发车 对私流水收开卡 ✨一月:210U ✨三月:240U ✨六月:270U ✨一年:350U ✨两年:420U ✨三年:480U ✨开卡至今 :550U 🔥 仅限私户 3-5天左右回单 对公流水 经侦对公流水 ✨一月:480U ✨三月:520U ✨六月:560U ✨一年:600U ✨两年:650U ✨三年:750U ✨开卡至今 :800U 保真不保漏 空单不收 其他有任何记录都收 上市公司 国企背景 国资控股 小贷城投融资不要 敏感单扣单 🙃🙃🙃🙃🙃🙃🙃 综合柜台开卡流水 个人开卡 😀😄😄😆 公司开卡 🥹😄😄😆 建设银行 农业银行 招商银行 交通银行 工商银行 民生银行 平安银行 3-7工作日回单(陆续回单) 空不收费、其他有任何数据都收费、 公户私户均无遗漏 无条数上限 公户(城投、融资、小贷、上市公司、国企、国企参股) 不要报,敏感扣单 ✅点击此处联系:@Fuchen

14 Aug 2026, 16:32 UTC43 viewsread 22 August 2026

车轨5+1 😃😄😄😆 提供车牌号 出最新一个月内100条行驶记录 注意:有的车没有车图 不满100条有记录,出单即收费 最近一个月没记录就往前推一个月 保真不保漏 ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

12 Aug 2026, 09:58 UTC46 viewsread 22 August 2026
Photo

停车库实时定位 😁😀😄😆单次 报单:提供车牌号 回单时间: 30分钟左右出单 文字带链接图片回单 注意:个别停车场系统无图 进库时间 时间:早上10.00-凌晨2.00 在线秒 可预约未来10天内出实时,10天内车进库就出 空不收 抓车抓人 比定位更加准确 ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

11 Aug 2026, 13:20 UTC44 viewsread 22 August 2026
File

手机轨迹系列 开普勒手机轨迹版 出全部 😁😀😄😆 半年内低于五条 免单 回单时间 : 当天/ 隔天回单 保真不保漏 开普勒版本因设备识别基于WIFI IP GPS APP软件 基站等 多重识别方式 结果直接导出未经过人为编辑,所以个别位置会有误导识别现象,产生经纬跳跃 结果以总体较多出现的位置为准。 经纬度替换位置 可以用这个链接替换: https://api.map.baidu.com/lbsapi/getpoint/index.html?qq-pf-to=pcqq.c2c ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

5 Aug 2026, 12:26 UTC59 viewsread 22 August 2026
Photo

版1车管所名下车 😁😀😆 全部给详情页 🈳不收费 版2 车管所名下车 😃😀😆 多辆车 给一个详情页 🈳不收费 非ETC渠道,专吃ETC剩菜 ETC🈳的可以报过来了 实测有的比公网还多2辆车 保遗漏 提供证据 可以免单 ✅点击此处联系:@Fucheng_CD 双向联系:@FuchengCD_bot

1 Aug 2026, 08:04 UTC58 views0 reactionsread 22 August 2026
Photo

犯罪服刑记录开 😉😀😆 当天隔天回 空给图收费

1 Aug 2026, 05:09 UTC55 viewsread 22 August 2026

无芒 银行流水 本周集合 周末发车 3-5天 回单 无盲经侦保遗漏流水 一月 270U 三月 300U 半年 330U 一年 380U 两年 430U 三年 500U 上线8000或9999 可以接三年之内的指定 柜台开卡流水 😀😄😄😆 建设招商工商中信平安 只要个户 下周一早上8点发车 建设当天隔天回 其他银行3-7工作日回 无遗漏保售后流水 有遗漏退款 柜台开卡流水 个人开卡 😀😁😄😆 公司开卡 🥹😃😄😆 建设银行 农业银行 招商银行 交通银行 工商银行 民生银行 平安银行 3-7工作日回单(陆续回单) 空不收费、其他有任何数据都收费、 公户私户均无遗漏 无条数上限 公户(城投、融资、小贷、上市公司、国企、国企参股) 不要报,敏感扣单

1 Aug 2026, 05:05 UTC48 viewsread 22 August 2026
Photo

三网话单~全网独家 一个月😉😀😄😆 两个月😀😀😄😆 三个月🥹😀😄😆 目前只能出通话号码 没有拨打时间 没有通话时长 亲测遗漏小(保真不保漏) 1~3天回单(基本隔天回单)

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

Posts edited after publishing

@fczxyw 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.

First edit seen
18 August 2026
Most recent edit
18 August 2026

Citation-graph rank

Citation-graph rank — 1,382,039 of 1,628,524entries 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“富城业务中心” (@fczxyw), 4,746 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/fczxyw.

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.