Telegram RegisterThe public register of Telegram

Channel

福利来供需@fugongxu

@fugongxu

2 usernames

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

63,065subscribers

-786 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001800296948
TypeChannel
Usernames@fllgq7 @fugongxu
Description本频道是福利来供求信息频道 福利来担保客服: @fuvipdb 福利来公群导航: @fuvipgq 福利来担保供需: @fllgq7 福利来免费代理: @fuvipvpn 福利来群管机器人: @fuvipgqbot 福利来客服机器人: @fuvipdbbot 福利来钱包机器人: @fuvipaybot 福利来东方汇实体娱乐厅(柬埔寨西港、缅北果敢老街都有实体现场,请老板们认准担保客服频道担保客服人员名单,谨防冒充!!!
Created2 June 2023measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/fugongxu

Growth

63,06563,85163,4587 August 2026 — 63,851 subscribers8 August 2026 — 63,828 subscribers9 August 2026 — 63,680 subscribers9 August 2026 — 63,583 subscribers10 August 2026 — 63,402 subscribers11 August 2026 — 63,297 subscribers12 August 2026 — 63,237 subscribers14 August 2026 — 63,065 subscribers7 August 202614 August 2026
8 measurements spanning 6 days, net -786. 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 62,947–63,969 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:5763,065-172
12 Aug 2026, 18:1763,237-60
11 Aug 2026, 20:4363,297-105
10 Aug 2026, 20:3263,402-181
9 Aug 2026, 21:3163,583-97
9 Aug 2026, 00:5563,680-148
8 Aug 2026, 00:2563,828-23
7 Aug 2026, 18:4563,851first reading

Engagement

2 posts held, back to 2 June 2023the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 19 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 29 October 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

29 Oct 2024, 15:28 UTC≈21,700 viewsread 14 August 2026
Photo

福利来供需频道感谢您的关注与陪伴 在这里,我们将满足用户的供应与需求,为普通用户打造一个真实、靠谱、前卫的资源平台,并为会员发布的供应与需求提供源源不断的流量支持。 为确保良好的频道氛围,我们设立了以下规则,请仔细阅读: 1️⃣收费金额:每条供需广告收取 38u/条。其他发布模式的收费标准:https://t.me/fuvipdb/5 2️⃣诚实守信:请确保发布内容真实,不得发布虚假广告与恶意链接。如一经查明,将立即下架且不退款。 3️⃣流量推送:推送的供需不仅会在我们合作的各个供需频道展示,我们还将对会员用户发布的供需进行单独且精准的客户资源流量扶持。 4️⃣责任纠纷:请注意,福利来供需不对除在我方公群上押注的公群负责人以外的交易方负责,交易请走福利来担保专群。 5️⃣咨询协助:如有疑问或需要协助,请随时联系担保客服:@fubb1、@fubb5、@fuvipdbbot。 请遵守以上规则,再次感谢您的关注与支持,

Showing the 2 most recent of 2 posts we hold for @fugongxu. 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 — 917,216 of 1,345,403entries 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 2 registered channels — 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“福利来供需@fugongxu” (@fugongxu), 63,065 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/fugongxu.

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.