Telegram RegisterThe public register of Telegram
Telegram profile photo for 地址生成器 模仿地址靓号

Channel

地址生成器 模仿地址靓号

@gengfu

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

19,422subscribers

+19,420 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002798598637
TypeChannel
Username@gengfu
Created9 August 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live6 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/gengfu

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 6 October 2026 and assigned it the closest of 31 fixed categories, at 85% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

220,08310,042.513 August 2026 — 2 subscribers13 August 2026 — 2 subscribers6 October 2026 — 20,081 subscribers10 October 2026 — 20,082 subscribers26 October 2026 — 20,083 subscribers4 November 2026 — 19,966 subscribers5 November 2026 — 19,758 subscribers6 November 2026 — 19,422 subscribers19,42213 August 20266 November 2026
8 measurements spanning 85 days, net +19,420. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 02:4019,422-336
5 Nov 2026, 02:3919,758-208
4 Nov 2026, 04:3819,966-117
26 Oct 2026, 07:2720,083+1
10 Oct 2026, 06:2020,082+1
6 Oct 2026, 03:1820,081+20,079
13 Aug 2026, 20:492no change
13 Aug 2026, 11:322first reading

Engagement

12 posts held, back to 9 August 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
—
no view readings in window
Avg views / post
—
no view readings
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 12 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 8 October 2026
Posts held12 (9 August 2025 – 8 October 2026)
Views total—
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 15:10 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

Video runtime
4m 33s
Average length
2m 17s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Oct 2026, 12:36 UTC43 viewsread 5 November 2026
Photo

波场地址 靓号生成器 trc20 trx能量 客服 @leyang永久频道 @h8999

3 Oct 2026, 17:00 UTC45 viewsread 5 November 2026

🟢USDT自动兑换TRX🔴 (转U自动回TRX,5U起换) 💹实时汇率 1 USDT = 2.6691 TRX 100 TRX = 28.6600 USDT 🔄自动兑换地址: TWEm3vGspdwA7YBkEsAED9prBAAAAAAAAA 🔺转U自动兑换TRX 🔺TRX换U请联系客服 @leyang 多功能机器人 @fjztrxbot

3 Oct 2026, 16:57 UTCviews —

地址生成器 模仿地址靓号 pinned «靓号生成器 模仿地址 能量租用 监听地址 trx闪兑 频道上粉 频道群组排名 飞机号 esim流量卡 会员代开 频道助力 机器人定制 群发软件 联系客服 @leyang 双向客服 @leyangbot 飞机号购买 @TXAABOT 能量会员购买 @fjztrxbot»

3 Oct 2026, 16:50 UTC39 viewsread 5 November 2026

【⚡️能量闪租】 🔸转账 3 Trx= 1 笔能量 🔸转账 6 Trx= 2 笔能量 1.向无U地址转账,需要双倍能量。 2.请在1小时内转账,否则过期 🔸闪租能量收款地址: TRrecWJkgXAtWxKuuDPX94H3Ts12345678 ➖➖➖➖➖➖➖➖➖ 💎 (点击地址自动复制) 波场地址定制 前三后五50u 半小时完成 波场地址定制 前四后五100u 10小时完成 波场地址定制 前五后五300u 10天内完成 其他靓号联系: @leyang 双向客服:@leyangkfbot 多功能机器人 @fjztrxbot

3 Oct 2026, 16:49 UTC26 viewsread 5 November 2026
Photo

🛜[ eSIM流量卡 ] 🛡优势 ├─无需实体卡闪电下发 ├─线上扫码即激活,出海商旅必备 ├─全球漫游网络无缝直连 └─拒绝低质中转,直连海外原生优质网络 ℹ使用教程: 点击查看 ⚠购买前必看 如忽略买错后果自负! 👇请选择您的操作! esim流量卡 飞机号 @TXAABOT

3 Oct 2026, 16:48 UTC21 viewsread 5 November 2026
Photo

【靓号】不在对波场靓号业务打压价格 为了让广大靓号爱好者付出的服务器成本不至于亏本 特下调靓号地址销售价格: 【8位靓号】 50U 8位豹子【英文小写】 58U 8位豹子【英文大写】 68U 8位豹子【数字1.2.3.4.5】 88U 8位豹子【数字6.7.8.9】 158U 8位顺子【步步高升号】 【顺子1-8 2-9】 【9位靓号】 158U 9位豹子【英文小写】 168U 9位豹子【英文大写】 188U 9位豹子【数字1.2.3.4.5】 328U 9位豹子【数字6.7.8.9】 588U 9位顺子【步步高升号】 【顺子1-9】 【10位靓号】 1288U 10位豹子【英文小写】 1388U 10位豹子【英文大写】 2088U 10位豹子【数字1.2.3.4.5】 888U 10位豹子【数字6.7.8.9】 2888U 10位顺子【…

3 Oct 2026, 16:47 UTC17 viewsread 5 November 2026
Video

手机【多签】转账演示视频 用【安全地址】控制【靓号地址】转账演示

3 Oct 2026, 16:47 UTC15 viewsread 5 November 2026
Video

手机更改【多签】权限演示视频 【苹果手机】无法更改 请用安卓手机或者电脑更改 电脑可以下载【雷电模拟器】模拟安卓

28 Sept 2026, 13:07 UTC16 viewsread 5 November 2026
Photo

https://fragment.com/ ——————————————— 用户名上链教程

9 Aug 2026, 17:15 UTC24 viewsread 5 November 2026

靓号生成器 模仿地址 能量租用 监听地址 trx闪兑 频道上粉 频道群组排名 飞机号 esim流量卡 会员代开 频道助力 机器人定制 群发软件 联系客服 @leyang 双向客服 @leyangbot 飞机号购买 @TXAABOT 能量会员购买 @fjztrxbot

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

Posts edited after publishing

@gengfu edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
3 November 2026
Most recent edit
3 November 2026

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.

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

“地址生成器 模仿地址靓号” (@gengfu), 19,422 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/gengfu.

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.