Telegram RegisterThe public register of Telegram

Channel

富力【NFT代售】

@shoushou

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

436subscribers

-56 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-1001656902147
TypeChannel
Username@shoushou
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/shoushou

Growth

4364924647 August 2026 — 492 subscribers7 August 2026 — 489 subscribers8 August 2026 — 489 subscribers15 August 2026 — 436 subscribers7 August 202615 August 2026
4 measurements spanning 7 days, net -56. 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 428–500 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 00:18436-53
8 Aug 2026, 04:30489no change
7 Aug 2026, 21:06489-3
7 Aug 2026, 13:36492first reading

Engagement

20 posts held, back to 1 January 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.

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 1 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
266.7%
👍133.3%

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 5 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 3reactions 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 1 January 2026 to 1 June 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

1 Jun 2026, 05:02 UTC641 views1 reactionsread 8 August 2026

出售4字id @mote 模特 喜欢的老板联系 @ruyi

1

15 May 2026, 06:23 UTC887 viewsread 8 August 2026

4字id出租 @kydb @kygq @kygx @apay @bpay @cpay @dpay @wpay(可挂机器人) 适合集团、担保使用 打包租全网最低 喜欢的老板联系 @ruyi

15 May 2026, 06:22 UTC830 viewsread 8 August 2026

@pqqqq @qmmmm @bssss @vqqqq @phhhh @peeee @nwwww @nqqqq @hwwww @ghhhh @fwwww @apppp @gqqqq 5位的字母 价不高 打包出 喜欢的老板联系 @ruyi

12 May 2026, 15:42 UTC754 viewsread 8 August 2026

@zhuantou 专投,砖头(专业投注,专业投诉) 喜欢的老板联系 @ruyi

7 May 2026, 14:54 UTC799 viewsread 8 August 2026

出售 @kydb @kygx @kygq 开元担保配套用户名,价不高,喜欢的老板喊我

13 Apr 2026, 05:21 UTC≈1,120 views1 reactionsread 8 August 2026

@b3333 @pqqqq @q0000 @qmmmm @f0000 @bssss @g4444 @vqqqq @q1111 @phhhh @q2222 @peeee @r0000 @nwwww @r4444 @nqqqq @r7777 @mpppp @t7777 @jqqqq @w9999 @hwwww @y2222 @ghhhh @z6666 @fwwww @z8888 @apppp @g5555 @p8888 @g7777 @l7777 @g9999 @l5555 @gqqqq 5位的字母+数字 价不高 喜欢的老板联系 @ruyi

1

12 Apr 2026, 12:01 UTC795 viewsread 8 August 2026

@kongliang 孔亮 @soubu 搜捕 @fugeng 福庚 @kangge 康哥 @zhange 战歌 展哥 @zhenge 震哥 @huangge 黄哥 @vipgege VIP哥哥 @laojun 老君 @liulan 浏览 @souhuo 搜获 @zhihui 智慧 指挥 @jiayong 家用 佳勇 @jingsao 警嫂 @liaotou 料头 @wangqun 王群 网群 @wuniang 舞娘 @chenqing 澄清 @zhongbai 钟摆 中百 @tiandang 天当 舔党 喜欢的老板联系 @ruyi

12 Apr 2026, 11:59 UTC672 viewsread 8 August 2026

支付行业好词 @feilv 费率 @madui 码队 @mashang 码商 @huadanshang 话单商 @huafei 话费 @dianfei 电费 @dianxin 电信 @rentouma 人头码 @zhipan 直盘 @zijinpan 资金盘 @yuansheng 原生 @zspay 战神支付 @zhuantou 砖头 @xitong_chuzu 系统_出租 @sifangsanfang 四方三方 @sanfang_sifang 三方四方 @huaqidanbao 花旗担保 @jinxiudanbao 锦绣担保 @zhaoyuangong 招员工 价格不贵 支付行业可以考虑入手 喜欢的老板联系 @ruyi

11 Apr 2026, 05:47 UTC622 viewsread 8 August 2026

@zijinpan 资金盘 @zhipan 直盘 价格不贵 喜欢的盘总联系 @ruyi

9 Apr 2026, 10:59 UTC607 views0 reactionsread 8 August 2026

代售 888 0188 8888 888 0688 8888 喜欢的老板联系 @ruyi

Showing the 12 most recent of 20 posts we hold for @shoushou. 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 — 670,521 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 6 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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“富力【NFT代售】” (@shoushou), 436 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/shoushou.

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.