Telegram RegisterThe public register of Telegram
Telegram profile photo for iiPay红包频道🧧

Channel

iiPay红包频道🧧

@iifufu

3 usernames

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

3,214subscribers

-23 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002602717513
TypeChannel
Usernames@app20 @iifufu @iihongbao
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/iifufu

Growth

3,2073,2373,2227 August 2026 — 3,237 subscribers7 August 2026 — 3,237 subscribers8 August 2026 — 3,237 subscribers8 August 2026 — 3,236 subscribers11 August 2026 — 3,219 subscribers11 August 2026 — 3,219 subscribers11 August 2026 — 3,217 subscribers14 August 2026 — 3,210 subscribers14 August 2026 — 3,210 subscribers15 August 2026 — 3,207 subscribers17 August 2026 — 3,207 subscribers18 August 2026 — 3,214 subscribers3,2147 August 202618 August 2026
12 measurements spanning 11 days, net -23. 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 3,203–3,242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 03:023,214+7
17 Aug 2026, 12:573,207no change
15 Aug 2026, 17:433,207-3
14 Aug 2026, 18:083,210no change
14 Aug 2026, 14:343,210-7
11 Aug 2026, 20:533,217-2
11 Aug 2026, 10:083,219no change
11 Aug 2026, 07:423,219-17
8 Aug 2026, 14:333,236-1
8 Aug 2026, 03:113,237no change
7 Aug 2026, 14:463,237no change
7 Aug 2026, 11:163,237first reading

Engagement

20 posts held, back to 3 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 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 20 posts for this entry, the most recent from 19 March 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

4 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4100.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 3 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 4reactions 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 3 March 2026 to 19 March 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

19 Mar 2026, 17:08 UTC≈1,330 views2 reactionsread 7 August 2026

【旺旺担保 项目交流大群 @jiaoliudq】发起了一个拼手气红包 💵总金额: 500 CNY 剩余: 50/50 领取条件:👉需入群才能领取红包

2

15 Mar 2026, 10:49 UTC≈1,410 viewsread 7 August 2026

【旺旺担保 NFT +888 交流群【限NFT+888进入】🚫禁止广告】发起了一个拼手气红包 💵总金额: 500 CNY 剩余: 50/50 领取条件:👉需入群才能领取红包

11 Mar 2026, 12:28 UTC988 viewsread 7 August 2026

【东南亚交流群_华人之光🇨🇳】发起了一个拼手气红包 💵总金额: 50 CNY 剩余: 50/50 领取条件:👉需入群才能领取红包

10 Mar 2026, 12:49 UTC790 views1 reactionsread 7 August 2026

【TG博彩社】发起了一个拼手气红包 💵总金额: 3000000 ii 剩余: 150/150 领取条件:👉需入群才能领取红包

1

10 Mar 2026, 12:28 UTC559 viewsread 7 August 2026

【缅甸妙瓦底交流群_不忘初心♨️】发起了一个拼手气红包 💵总金额: 50 CNY 剩余: 50/50 领取条件:👉需入群才能领取红包

10 Mar 2026, 10:41 UTC462 viewsread 7 August 2026

【】发起了一个拼手气红包 💵总金额: 80 CNY 剩余: 49/50 领取条件:👉需入群才能领取红包

9 Mar 2026, 10:30 UTC411 viewsread 7 August 2026

【君临天下-晚上10点舞蹈大秀】发起了一个拼手气红包 💵总金额: 89 CNY 剩余: 80/80 领取条件:👉需入群才能领取红包

7 Mar 2026, 06:52 UTC429 viewsread 7 August 2026

【BBa卡商聚集地】发起了一个拼手气红包 💵总金额: 5 USDT 剩余: 50/50 领取条件:👉需入群才能领取红包

7 Mar 2026, 03:28 UTC452 viewsread 7 August 2026

【呆呆萌萌的流量基地】发起了一个拼手气红包 💵总金额: 324 CNY 剩余: 120/120 领取条件:👉需入群才能领取红包

7 Mar 2026, 03:18 UTC401 viewsread 7 August 2026

【东南亚吃瓜群众聊天群】发起了一个拼手气红包 💵总金额: 588 CNY 剩余: 128/128 领取条件:👉需入群才能领取红包

6 Mar 2026, 12:52 UTC394 viewsread 7 August 2026

【君临天下-9点抽奖送礼物】发起了一个拼手气红包 💵总金额: 68 CNY 剩余: 50/50 领取条件:👉需入群才能领取红包

6 Mar 2026, 06:25 UTC341 viewsread 7 August 2026

【小雨项目之家】发起了一个拼手气红包 💵总金额: 5 USDT 剩余: 50/50 领取条件:👉需入群才能领取红包

Showing the 12 most recent of 20 posts we hold for @iifufu. 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 — 880,797 of 1,548,671entries 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.

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

“iiPay红包频道🧧” (@iifufu), 3,214 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/iifufu.

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.