Telegram RegisterThe public register of Telegram
Telegram profile photo for 起点福利大家庭 @kkpay

Channel

起点福利大家庭 @kkpay

@LDL123

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

16,207subscribers

+719 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004403546375
TypeChannel
Username@LDL123
Description红包/抽奖/福利
Created20 July 2026measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live1 September 2026
Measurements held25
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/LDL123

Growth

15,48816,27815,8836 August 2026 — 15,488 subscribers6 August 2026 — 15,508 subscribers7 August 2026 — 15,536 subscribers8 August 2026 — 15,621 subscribers9 August 2026 — 15,674 subscribers10 August 2026 — 15,739 subscribers11 August 2026 — 15,786 subscribers12 August 2026 — 15,870 subscribers13 August 2026 — 15,945 subscribers14 August 2026 — 16,029 subscribers16 August 2026 — 16,060 subscribers17 August 2026 — 16,113 subscribers18 August 2026 — 16,149 subscribers19 August 2026 — 16,144 subscribers20 August 2026 — 16,159 subscribers22 August 2026 — 16,199 subscribers23 August 2026 — 16,245 subscribers25 August 2026 — 16,263 subscribers26 August 2026 — 16,278 subscribers27 August 2026 — 16,269 subscribers28 August 2026 — 16,251 subscribers29 August 2026 — 16,239 subscribers30 August 2026 — 16,213 subscribers31 August 2026 — 16,208 subscribers1 September 2026 — 16,207 subscribers16,2076 August 20261 September 2026
25 measurements spanning 26 days, net +719. 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 15,370–16,397 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
1 Sept 2026, 11:0416,207-1
31 Aug 2026, 14:0216,208-5
30 Aug 2026, 12:0216,213-26
29 Aug 2026, 08:3316,239-12
28 Aug 2026, 05:5416,251-18
27 Aug 2026, 04:4516,269-9
26 Aug 2026, 03:1116,278+15
25 Aug 2026, 04:2316,263+18
23 Aug 2026, 23:3916,245+46
22 Aug 2026, 09:5816,199+40
20 Aug 2026, 22:5516,159+15
19 Aug 2026, 19:2816,144-5
18 Aug 2026, 19:1316,149+36
17 Aug 2026, 20:0316,113+53
16 Aug 2026, 15:0616,060+31
14 Aug 2026, 19:3816,029+84
13 Aug 2026, 08:3615,945+75
12 Aug 2026, 08:5315,870+84
11 Aug 2026, 06:0815,786+47
10 Aug 2026, 06:4015,739first reading

Engagement

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

ERR · 30 days
18.1%
avg views ÷ 16,207 subscribers
Avg views / post
2,940
1 post measured
Reaction rate
0.068%
reactions ÷ views · ER floor
Posts in window
1
of 2 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 18 August 2026
Posts held2 (20 July 202618 August 2026)
Views total2,940
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 03:50 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.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 2 September 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.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 2 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 20 July 2026 to 18 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

18 Aug 2026, 21:58 UTC≈2,940 views2 reactionsread 2 September 2026

⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 有收款码能收钱的来 支/微收款 一天5000 小额代收 日赚7000 有码的来 一天5000 捡钱了 早上赚了5000 客服:https://t.me/saimin 双向联系: @xxjdjqrbot ↪️上压10w人民币对接群:https://t.me/+S46CyXoEyF5iYWU1 支持付款🐛:👍👍👍👍👍

2

Showing the 2 most recent of 2 posts we hold for @LDL123. 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,518 of 1,629,535 entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

𝐑𝐄𝐗官方频道【注意置顶】
@REXNBQJ · 46,693
51 posts
小羽的窝
@SWNBNB96 · 23,693
47 posts
小熊猫官方频道(疯狂更新)
@REBAC8 · 110,351
46 posts
落春秋加速
@LikeLCQ · 22,224
44 posts
❤️公益辅助分享❤️
@wjhshsne · 47,461
44 posts
02端口官方频道
@dk02nb · 26,662
41 posts
𝑵𝑻𝑯𝑴𝑶𝑫🇨🇳
@NTH_MODS · 16,428
41 posts
Shrem上色内透改文件
@Shrem520 · 51,307
40 posts
追猎杯通知频道🥤
@ZLBNB666 · 50,695
40 posts
AS Game 官方频道
@ASZZGF1 · 24,958
39 posts
仁济改文件主频道
@byrj91 · 49,127
39 posts
巴巴托斯公益内核频道
@BBTSNHNB1 · 19,115
38 posts
🔥分享软件破解团队🔥
@dddailik · 48,114
38 posts
UE 极客核心 | 全球端手游联动
@UE_Ultra · 33,610
38 posts
异世界
@bitpojie · 13,621
37 posts
破晓-主频道 [更新看置顶]
@bxwsy · 26,694
37 posts
辞忧的小窝[冲15k]
@KSCYNB · 14,284
37 posts
裁决者(主频道)
@zimunb6 · 14,350
37 posts
XARG中国官方频道
@BYBX666 · 13,497
36 posts
鹿安内核辅助破解(和平王者CFM暗区使命无畏三角洲PUBG内核)
@rg99999 · 16,693
34 posts
三角洲【天才Z】内部公益中
@tczgf · 11,241
33 posts
冰雪泛滥文件主频道🇨🇳
@BaiLUOXUEGWJ · 33,210
32 posts
𝙏𝙞𝙜𝙚𝙧 - 𝘾𝙉官方频道🇨🇳
@TigerCN_BY · 10,032
32 posts
七辰官方频道
@yuenb886s · 28,230
32 posts
仁济端口
@rjdk6 · 14,958
31 posts
落叶公益内核
@luoyenb521 · 73,629
30 posts
QZ官方频道【沉淀中】
@QZMODN · 30,319
30 posts
相亲相碍一家人
@Xo_eps · 10,629
30 posts
竹叶海改文件频道
@ASGA8 · 141,368
29 posts
HTY改文件频道
@HTYS1 · 10,154
29 posts
熊大公益直装[官方频道]
@XIANHE_CHEAT · 11,567
24 posts
傲寒主频道(长期公益🇨🇳)
@AHGFPD · 61,604
23 posts
️小黄改文件主频道🇨🇳
@ASXH8 · 31,226
23 posts
CAT MOD
@CATMOD · 2,643
22 posts
小黄人MOD【剑桥版本】
@liizeNB666 · 17
22 posts
SEVEN公益改文件💤
@sevennb1 · 8,467
20 posts
椎名真昼主频道
@XBZZYA · 13,991
20 posts
ZIPpad瓦-三角洲公益解密
@ZIPpad · 9,997
20 posts
Doro主频道
@XuanXkk · 22,341
18 posts
乐执学生党
@DazhiMh · 17,808
17 posts
JS文件主频道
@JSAI866 · 23,164
17 posts
Dra-主频道
@Drabanl · 37,366
16 posts
AS Game 官方频道 🇨🇳
@DSCHEAT8 · 13,886
16 posts
幻灭公益主频道
@HuanMiePD · 9,909
16 posts
神楚项目通知频道
@SCNBDN · 18,641
16 posts
七辰大家庭
@qcnb991 · 6,977
15 posts
猪猪侠官方正版频道(冲30k)
@lbmhnb · 6,688
12 posts
龙之国/龙将军唯一官方频道
@NA88lp · 32,065
11 posts
零龙资源分享(三角形PUBG和平无畏契约王者荣耀)
@xubaiwj · 10,638
11 posts
广州市政府
@GZSZF · 6,283
10 posts
VicTorious公益内核频道
@VTKernel · 54,854
10 posts
币子导航频道
@bizinb · 7,152
7 posts
风云主频道
@FYNB2 · 13,054
7 posts
币子频道
@bizinb8 · 6,114
6 posts
缘之空主频道
@QZMH6666 · 7,782
5 posts
七小辰官方频道
@bdhnb995 · 6,834
4 posts
轩少和平项目主频道
@XSDKNB · 17,332
4 posts
苦瓜
@kugua524 · 3,641
3 posts
转转数据号『低价号源』
@HERONB88 · 17,185
2 posts
芒果直装🇨🇳『PUBGM』
@MANGGUOTZ · 4,592
2 posts
七色花数据号(0.07白号)
@NLXMNB · 1,893
2 posts
雾鱼直装官方频道
@siyinb66 · 2,993
2 posts
菠萝纯手打8级
@BLZHNB · 4,487
1 post
千痕拦截主频道[冲刺1.5k]
@GDDNB666 · 1,151
1 post
GK全防and byte内核🔥
@GKKING666 · 4,660
1 post
和平精英落叶直装
@gtqny · 2,377
1 post
幻影业务频道
@huanyingyyds · 2,466
1 post
七辰改文件🇨🇳
@KKWZNB8 · 5,832
1 post
劳改犯追踪
@LGFZZ · 3,197
1 post
NTH
@NTHMODLk · 2,546
1 post
七辰的朋友圈
@QCMOD520 · 2,010
1 post
抢劫犯追踪
@SSNP88 · 2,489
1 post
小黄鸭主频道
@XHYNH · 4,156
1 post
七辰项目导航[唯一正版]
@ykdknb · 4,313
1 post

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“起点福利大家庭 @kkpay” (@LDL123), 16,207 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/LDL123.

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.