Telegram RegisterThe public register of Telegram
Telegram profile photo for 富贵供需 𝟏𝟎𝐔一条 自助发布 @𝐅𝐆𝐏𝐃𝐛𝐨𝐭

Channel

富贵供需 𝟏𝟎𝐔一条 自助发布 @𝐅𝐆𝐏𝐃𝐛𝐨𝐭

@FGgongxu

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

29,296subscribers

+3,541 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1002236043618
TypeChannel
Username@FGgongxu
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live28 October 2026
Measurements held43
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/FGgongxu

Topic

Gambling & betting — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 78% 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.

Growth

25,71729,29627,506.518 August 2026 — 25,755 subscribers18 August 2026 — 25,764 subscribers19 August 2026 — 25,717 subscribers20 August 2026 — 25,766 subscribers21 August 2026 — 25,848 subscribers22 August 2026 — 25,924 subscribers24 August 2026 — 25,921 subscribers25 August 2026 — 25,982 subscribers26 August 2026 — 26,040 subscribers27 August 2026 — 26,208 subscribers28 August 2026 — 26,257 subscribers29 August 2026 — 26,206 subscribers30 August 2026 — 26,194 subscribers31 August 2026 — 26,153 subscribers1 September 2026 — 26,327 subscribers2 September 2026 — 26,445 subscribers3 September 2026 — 26,450 subscribers5 September 2026 — 26,476 subscribers8 September 2026 — 26,550 subscribers11 September 2026 — 26,458 subscribers13 September 2026 — 26,297 subscribers15 September 2026 — 26,341 subscribers16 September 2026 — 26,455 subscribers19 September 2026 — 26,547 subscribers26 September 2026 — 26,885 subscribers4 October 2026 — 27,641 subscribers8 October 2026 — 27,905 subscribers13 October 2026 — 28,504 subscribers14 October 2026 — 28,631 subscribers15 October 2026 — 28,669 subscribers16 October 2026 — 28,725 subscribers17 October 2026 — 28,781 subscribers18 October 2026 — 28,799 subscribers19 October 2026 — 28,878 subscribers20 October 2026 — 28,899 subscribers22 October 2026 — 28,906 subscribers23 October 2026 — 28,974 subscribers23 October 2026 — 29,051 subscribers24 October 2026 — 29,086 subscribers25 October 2026 — 29,140 subscribers26 October 2026 — 29,160 subscribers27 October 2026 — 29,192 subscribers28 October 2026 — 29,296 subscribers18 August 202628 October 2026
43 measurements spanning 71 days, net +3,541. 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 25,180–29,833 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 43
Measured (UTC)SubscribersChange
28 Oct 2026, 17:1829,296+104
27 Oct 2026, 19:0929,192+32
26 Oct 2026, 16:4429,160+20
25 Oct 2026, 19:5029,140+54
24 Oct 2026, 21:1029,086+35
23 Oct 2026, 22:5529,051+77
23 Oct 2026, 00:3628,974+68
22 Oct 2026, 02:1828,906+7
20 Oct 2026, 17:3828,899+21
19 Oct 2026, 15:5828,878+79
18 Oct 2026, 16:5628,799+18
17 Oct 2026, 19:4728,781+56
16 Oct 2026, 17:4828,725+56
15 Oct 2026, 18:3728,669+38
14 Oct 2026, 17:4728,631+127
13 Oct 2026, 07:0028,504+599
8 Oct 2026, 23:0227,905+264
4 Oct 2026, 15:0027,641+756
26 Sept 2026, 13:2026,885+338
19 Sept 2026, 13:1726,547first reading

Engagement

573 posts held, back to 17 August 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 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.19%
avg views ÷ 29,296 subscribers
Avg views / post
349
213 posts measured
Reaction rate
0.297%
reactions ÷ views · ER floor
Posts in window
213
of 573 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 7 of 213 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 27 October 2026
Posts held573 (17 August 2026 – 27 October 2026)
Views total74,257
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Oct 2026, 07:07 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.

Reaction mix

14 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 64.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤964.3%
🌭17.14%
👎17.14%
💔17.14%
🙊17.14%
🦄17.14%

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 15 of the 573 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 573 most recent posts we hold, published 17 August 2026 to 27 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.

Recent posts

27 Oct 2026, 23:38 UTC305 viewsread 28 October 2026

💎项目名称:[好运来天眼查] 一手渠道 全年秒查 💎项目介绍:👮‍♀️司法冻结/网逃仁员/案件记录 👮🏽手机定位/查身份证/全家戸籍 👮‍♀️银行流水/微信提取/手机反查 👮🏽照片找仁/开房记录/同住记录 👮‍♀️婚姻记录/微信实名/支付实名 👮🏽查出入境/航班记录/高铁记录 👮‍♀️名下号码/通话记录/名下车房 💎项目价格:覆盖所有业务,想查什么,直接咨询 ━━━━━━━━━━━━━ ✈️联系方式:@HYLTYC ✈️群组频道:@HYLTYC ━━━━━━━━━━━━━ ♻️该用户:【累计发广告182次】 ♻️关键词: #一手 #定位 #微信 #支付 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 21:09 UTC370 viewsread 28 October 2026

💎项目名称:提莫租号/出租888匿名号码、靓号💎 💎项目介绍:1:具备防封号,无注销,永不失联,💎 2:匿名性,官方发售无需手机号码,安全私密💎 3:身份的象征,业务对接增加与客户的信任感 💎 4:用于接粉,俗称不死号!!! 💎项目价格:10+ ━━━━━━━━━━━━━ ✈️联系方式:@timo ✈️群组频道:@niminghaoma ━━━━━━━━━━━━━ ♻️该用户:【累计发广告330次】 ♻️关键词: #租号 #出租 #靓号 #接粉 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 19:55 UTC229 viewsread 28 October 2026

💎项目名称:上码❤️‍🔥各类码❤️‍🔥24h单子❤️‍🔥正常收量‼️每日结算‼️❣️各类码❣️ 上天马单价盘持续收量🆘结算只看真假不看产值🆘 ‼️真粉包结 大量来色粉 收一切大中小平台 无限收量 ‼️ 💎项目介绍:🦃主收一切大中小全部姿势 所有小平台全部系列姿势色粉 上码 上Q群 付费平台和任何上粉形式 能打出来色粉都收🦥 🦔招收各种新型平台 大中小型平台 S粉 各种平台都可以来不限渠道上码 上Q 上Q群 全时段 安排快捷 结算迅速 只要真粉 包结算 平台 量 一次过来报完我给你价或者自带价 无需介绍自己 别来闲聊 💎项目价格:15-27 ━━━━━━━━━━━━━ ✈️联系方式:@syune ✈️群组频道:https://t.me/evyvv ━━━━━━━━━━━━━ ♻️该用户:【累计发广告148次】 ♻️关键词: #天马 #Q群 ━━━━━━━━━━━━━ ‼️以任何理由不走担…

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 19:45 UTC301 viewsread 28 October 2026

💎项目名称:大量出40+死绑ini缓存星月混合,可扫怀旧,质量ok 💎项目介绍:全天注册死绑缓存处,可验证,可附近人,支持预订 💎项目价格:1+ ━━━━━━━━━━━━━ ✈️联系方式:@tiayu ✈️群组频道:https://t.me/tianyu888168 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告24次】 ♻️关键词: #验证|#死绑|#缓存|#注册|#星月 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 19:13 UTC313 viewsread 28 October 2026

💎项目名称:技术,运维,源码,开发,搭建,盘口(资金盘,PC刷单,海外商城入驻,币交易所等)支持多语言 承接前端UI更换,增减后端功能等项目二次开发(可定制开发复制一切盘口) 💎项目介绍:一手大厂团队,10年顶尖技术水平,程序员,24H在线实时维护,确保平台代码稳定上线运营。 💎项目价格:详谈 ━━━━━━━━━━━━━ ✈️联系方式:@qqq783 ✈️群组频道:@qqq783 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告160次】 ♻️关键词: #技术 #源码 #开发 #一手 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 18:27 UTC299 viewsread 28 October 2026

💎项目名称:大量出恢复星月 强提星月 出缓存三无ini缓存 可以绑卡。速来老板 💎项目介绍:无限收私人米正 , 只要是米正就可以 , 泄密米正也行。 💎项目价格:1 ━━━━━━━━━━━━━ ✈️联系方式:@shusheng868 ✈️群组频道:@shusheng868 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告18次】 ♻️关键词: #恢复|#三无|#强提|#私人|#缓存|#星月 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 18:14 UTC311 viewsread 28 October 2026

💎项目名称:免sm国内流量卡 香港流量卡 随身设备 💎项目介绍:专注国内流量卡,香港流量卡,香港注册卡,随身设备一张也发货 一手资源,全天在线,稳定售后成交只是开始,服务永无止境! 💎项目价格:2+ ━━━━━━━━━━━━━ ✈️联系方式:@bingxin ✈️群组频道:@bingnb ━━━━━━━━━━━━━ ♻️该用户:【累计发广告143次】 ♻️关键词: #流量卡 #一手 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 17:46 UTC337 viewsread 28 October 2026

💎项目名称:出 接码 注册 qq。每天3000+卡接码注册,人工接码。 💎项目介绍:另出三网原始卡回流老Q~留卡5-7天,质量嘎嘎硬 【星星85月亮95太阳145】 【注册qq来跑量客户对接 手工缓存打粉~等等业务】 【注册QQ营业时间中午12点到凌晨4点】 💎项目价格:私聊 ━━━━━━━━━━━━━ ✈️联系方式:@Sy_5889 @Damai66666666 ✈️群组频道:https://sy5889qq.top/shop ━━━━━━━━━━━━━ ♻️该用户:【累计发广告12次】 ♻️关键词: #QQ|#回流|#三网|#缓存|#粉|#注册|#手工|#星星|#月亮|#太阳 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 17:19 UTC302 viewsread 28 October 2026

💎项目名称:收全系色粉上天马云 💎项目介绍:收全系色粉上天马云,待遇拉满,结账稳定,只看基础数据,真粉不清不扣无套路,主打实时单,24h单子也有,码子丝滑,过滤你说了算,无限开码!带稳定结算记录跳槽单价➕1➕2➕3,绝不还价! 💎项目价格:待遇拉满 ━━━━━━━━━━━━━ ✈️联系方式:@bz0708 ✈️群组频道:https://t.me/+Tdd0F2jqdCc4NzQ9 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告79次】 ♻️关键词: #色粉 #数据 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 16:23 UTC321 viewsread 28 October 2026

💎项目名称:500w信誉买家,大量收快手新参绑卡号(日需2/3000)长期稳定的手子来。 💎项目介绍:每天稳定包量 💎项目价格:x ━━━━━━━━━━━━━ ✈️联系方式:@yizhang118 ✈️群组频道:@yizhang118 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告15次】 ♻️关键词: #快手 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 15:45 UTC339 viewsread 28 October 2026

💎项目名称:收色粉 💎项目介绍:高价收色粉 Q系列 小红书 快手采集 抖音采集 抖音私信等 收全渠道色粉 惨假的不要 24小时上码 稳定打手联系 量大可谈包结算 直接包养 卡密丝滑 款项稳定 机房联系 💎项目价格:12-20 ━━━━━━━━━━━━━ ✈️联系方式:@bosaidong ✈️群组频道:@bsd188 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告180次】 ♻️关键词: #抖音 #快手 #粉 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

27 Oct 2026, 15:09 UTC241 viewsread 28 October 2026

💎项目名称:收全系色粉上天马云 💎项目介绍:收全系色粉上天马云,待遇拉满,结账稳定,只看基础数据,真粉不清不扣无套路,主打实时单,24h单子也有,码子丝滑,过滤你说了算,无限开码!带稳定结算记录跳槽单价➕1➕2➕3,绝不还价! 💎项目价格:待遇拉满 ━━━━━━━━━━━━━ ✈️联系方式:@bz0708 ✈️群组频道:https://t.me/+Tdd0F2jqdCc4NzQ9 ━━━━━━━━━━━━━ ♻️该用户:【累计发广告78次】 ♻️关键词: #色粉 #数据 ━━━━━━━━━━━━━ ‼️以任何理由不走担保的都是骗子 ‼️私下交易100%会被骗请勿存侥幸

Signed 富贵担保|供需发布|机器人

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

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

“富贵供需 𝟏𝟎𝐔一条 自助发布 @𝐅𝐆𝐏𝐃𝐛𝐨𝐭” (@FGgongxu), 29,296 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/FGgongxu.

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.