Telegram RegisterThe public register of Telegram

Channel

富力集团🌈支付行业供需频道

@fuligq

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

891subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001877023591
TypeChannel
Username@fuligq
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/fuligq

Growth

891892891.57 August 2026 — 892 subscribers8 August 2026 — 892 subscribers15 August 2026 — 891 subscribers7 August 202615 August 2026
3 measurements spanning 7 days, net -1. 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 891–892 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:26891-1
8 Aug 2026, 01:04892no change
7 Aug 2026, 18:44892first reading

Engagement

20 posts held, back to 29 October 2025the 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
146.5%
avg views ÷ 891 subscribers
Avg views / post
1,310
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
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 6 August 2026
Posts held20 (29 October 20256 August 2026)
Views total2,610
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:04 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.0%

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

Measured over the 20 most recent posts we hold, published 29 October 2025 to 6 August 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

6 Aug 2026, 12:23 UTC≈1,200 viewsread 8 August 2026

料性:跑BC 直付通 要求:上压50000u跑量20万一下发 只招实力派码商,垫不起资金的别来问,记者勿扰! 需要准备资料: 身份证正反面 支付宝号 手机号 提前备好U对接好承兑,只要一开工就不能停,中途停容易死户 招实力车队,我方提供独家收款技术! 一个支付宝可跑300万➕ 需要码商垫资金 秒到支付宝余额,过点结算 正常跑没有卡钱情况! 有实力的来合作,点位好商量! 我方只要求本金充足,户多就行! 看好广告在联系我,炮嘴勿扰谢谢 集团量 @GYNIU8 @guangyuniu888 认准tg888、

20 Jul 2026, 15:04 UTC≈1,410 viewsread 8 August 2026

❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ 🥰汇诚Pay🥰🥰🥰专注BC 🥰 上海交通卡核销 🥰 香港八达通核销 🥰 七鲜礼品卡核销 🥰 盒马礼品卡核销 🥰 京东E卡核销 😃各类交通卡核销 😃各类卡密核销 ❤️各类有实力交通卡只要你能核销 ❤️实力靠谱核销优先,你能吃多少我就能做多少。 ❤️实力码队,产品多。 🥰🥰🥰🥰 @Hczx1 @Hckl66

14 Jun 2026, 12:56 UTC≈1,700 viewsread 8 August 2026

急需支付宝码商团队 支持担保优先 企业码 量大不罚站 欢迎中介 代理 咨询问价 老牌广宇 信誉 @guangyuniu888

12 Jun 2026, 12:17 UTC≈1,670 viewsread 8 August 2026

寻一手自营原生 10-100纯企业原生 10-500 量大不墨迹支持担保优先 多手勿扰 不纯不要 老牌广宇支付信誉 https://t.me/guangyuniu888

9 Feb 2026, 17:05 UTC≈2,780 viewsread 8 August 2026

自营一手 金条 uid收量 费率冰点 支持担保 脸熟预付 !!!@shihui

27 Jan 2026, 09:06 UTC≈2,850 viewsread 8 August 2026

资金产品收点量 资金产品 原生 费率2.5 u0.12 金额100-500 成功率60+ 联系人:https://t.me/HFNo1

25 Jan 2026, 13:48 UTC≈2,560 viewsread 8 August 2026

资金产品收点量 资金产品 原生 费率2.5 u0.12 金额100-500 成功率60+ 联系人:https://t.me/HFNo1

18 Jan 2026, 09:29 UTC≈2,210 viewsread 8 August 2026

实力 老牌支付宝码车,稳定供应,码多回u快,找纯bc盘口量,联系人:@LYgg444

9 Jan 2026, 09:10 UTC≈2,220 viewsread 8 August 2026

💫 土豆支付 当前开放产品 ➖➖➖💫 😀😀 😀😀其他专区💫➖➖➖ 233 😂银联扫码100-500 限额:100-500 250 😀云闪付红包100-499,需勾取【无需领取即可到账】没有勾选无法到账三天自动退回 266 😂【❤️AFB自营,高成功率❤️】支付宝转卡100-2000,禁卡转卡,卡转卡不退不补,司法1比1,放内层。 限额:100-2000 501 😂数字人民币编码转账50-5000 限额:50-5000 ➖➖➖💫 😂支付宝专区💫➖➖➖ 811 😀天猫直付10,20,30,50,100,200,300 限额:10,20,30,50,100,200,300 1111 😂😀支付宝话费50,100,200,抗投诉,120秒内支付,超时支付不补 限额:50,100,200 1221 😂【❤️AFB自营,高成功率❤️】支付宝收款码_综合288-20000,不抗投诉 限额:288-20000 1232 😂

2 Jan 2026, 10:12 UTC≈1,880 viewsread 8 August 2026

收 以下话单 移动 😘联通😘电信 😘网厅😘旗舰👌天猫👌 😘无限收三网话单🔠 (回U优先) 联系 @DCwu789

12 Dec 2025, 14:37 UTC≈2,060 viewsread 8 August 2026

承接-支付宝余额-余额宝-微信零钱-零钱通-或者支付宝微信卡出资金。(无视任何料) BC博彩类-卡转卡-公对公-公对私 现金-取手都支持! 外贸收款单 企业支付宝 安全法 小额担保 国外2D3D通道 全国妹子上门 手输机,碰碰机,一切Pos 各种境外码丝滑码~财富热线专员 @YzF518

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

Citation-graph rank

Citation-graph rank — 1,122,688 of 1,350,102entries 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“富力集团🌈支付行业供需频道” (@fuligq), 891 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/fuligq.

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.