Telegram RegisterThe public register of Telegram
Telegram profile photo for 支付资源供需整合

Channel

支付资源供需整合

@FABUGX

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

12,517subscribers

-54 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1001634722643
TypeChannel
Username@FABUGX
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live17 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/FABUGX

Growth

12,51712,57112,54417 Aug 2026, 14:45 — 12,571 subscribers17 Aug 2026, 20:18 — 12,517 subscribers17 Aug 2026, 14:4517 Aug 2026, 20:18
2 measurements taken within a single day, net -54. 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 12,509–12,579 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 20:1812,517-54
17 Aug 2026, 14:4512,571first reading

Engagement

20 posts held, back to 3 May 2026the 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
8.07%
avg views ÷ 12,517 subscribers
Avg views / post
1,010
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
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 15 August 2026
Posts held20 (3 May 202615 August 2026)
Views total2,021
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 14:45 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

15 Aug 2026, 05:19 UTC881 viewsread 17 August 2026
Photo

TGAI GPT让你简单快速解决问题 集成GPT所有版本 @TGAIFWBOT P图等等,任何问题都可以实现处理! 无需注册,无需繁琐,直接使用!

5 Aug 2026, 05:09 UTCviews —

支付资源供需整合 pinned «广告一条50u 打广告的商户,支持资源直推,会对内容进行推荐介绍,资源整合。 我会进行推荐,并且介绍。 广告发联系 @DH6878 优先联系机器人 @TGZFVIPBOT»

5 Aug 2026, 05:05 UTC≈1,140 viewsread 17 August 2026

广告一条50u 打广告的商户,支持资源直推,会对内容进行推荐介绍,资源整合。 我会进行推荐,并且介绍。 广告发联系 @DH6878 优先联系机器人 @TGZFVIPBOT

9 Jul 2026, 05:19 UTC≈1,000 viewsread 17 August 2026

【需】 财神cp盘口,来码车队,挂码后台,会员一对一充值! 支持验盘,大小车都要!纯量,点位置顶! 支付宝码,微信码,聚合码,经营码,都要! 预付直压来谈!(不接受的勿扰) 联系人:@DH6878 发广告联系 @DH6878

16 Jun 2026, 10:32 UTC885 viewsread 17 August 2026

【需】 业务名称:需二道支付宝承兑 业务介绍:来个人支付宝二道承兑车,绑店铺,货款三方平台提现出。底料常规内,鱼看不到店铺信息。之前接过店铺款的,懂得来。带汇率,小车、8手车、脑残骗子车勿扰,上大押的来。 联系人:@TMTM518 发广告联系 @DH6878

31 May 2026, 18:47 UTC995 viewsread 17 August 2026

暂时没空发布,有学徒要学,频道安排给你发布,资源安排对接! 招收学徒,分配业务,发布资源费用可以分配给学徒赚。 有意向可以联系我 @DH6878

19 May 2026, 08:01 UTC≈1,040 viewsread 17 August 2026

【供】 点位💰50,招工程料拿现车队,维护时间久,风险低,指定地点拿现金回U,多地可以介绍承兑,免去车队换u烦恼 1:操作简单,拿现金完成回款即可,有一两个小弟即可做 2:量大,城市选择性多,每天保量,不足保量正常赔付 3:押金7000U起拉专群交易可双押保量,保跑空,全国多地需要跟车承兑,欢迎承兑对接 联系人:@xigua78787 @qingtian6161 发广告联系 @DH6878

15 May 2026, 06:04 UTC≈1,060 viewsread 17 August 2026

【供】 业务名称:蒙古,秘鲁,约旦,摩洛哥 、土耳其 叙利亚 ,伊拉克,哥伦比亚,埃塞俄比亚 源头收量 可专卡 业务介绍: 海外源头一手冰价 联系人:@qpay19999 发广告联系 @DH6878

14 May 2026, 06:02 UTC988 viewsread 17 August 2026

【供】 业务名称::企业认证公众号 业务介绍:服务号满月以上、视频号蓝v。企业微信绿标主体,转让、超管、扫客服 联系人:@jgg77655 发广告联系 @DH6878

12 May 2026, 09:01 UTC999 viewsread 17 August 2026

【供】 业务名称:出国内全行业 数据dpi sdk 业务介绍:博彩.股票. 贷款 期货 可以指定台子出数 400电话进线采集,提供同行400电话或手机号 抖音号.快手号.小红书号匹配手机号 苹果im短信 可发bc 源头出数,问价不亏 联系人: @sssy001 发广告联系 @DH6878

11 May 2026, 02:23 UTC≈1,000 viewsread 17 August 2026

【需】 业务名称:天鸿财富只深耕(滴滴现金)这一个领域 业务介绍:一手常规滴滴现金直盘通道(专注且专业) 诚招全国滴滴现金车无接触引导会员放货! 全程无接触不露面取货:汇率置顶.安全至上. 欢迎全国滴滴现金固定车.移动车前来合作稳稳赢!汇率8.3-8.8 天天助你打满! 联系人:@thcf888 发广告联系 @DH6878

9 May 2026, 10:58 UTC865 viewsread 17 August 2026

【需】 业务名称:精聊码接回U车队 业务介绍:优 势:本公司致力对接亚洲中国区精聊业务,保司法客诉,欢迎各大车队、中介、散户咨询问价 联系方式: @qq9863 @fafafa88890 @hd9899 发广告联系 @DH6878

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“支付资源供需整合” (@FABUGX), 12,517 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/FABUGX.

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.