Channel
@lefuzf
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
257subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001923992384 |
|---|---|
| Type | Channel |
| Username | @lefuzf |
| Description | 上门换汇 赌场换汇 |
| Created | 25 June 2023 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lefuzf |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 09:17 | 257 | no change |
| 8 Aug 2026, 07:16 | 257 | first reading |
7 posts held, back to 25 June 2023 — the 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.
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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 7 (25 June 2023 – 4 August 2026) |
| Views total | 3 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:17 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
4 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 50.0% | |
| 👍 | 1 | 25.0% | |
| 🤔 | 1 | 25.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 4 of the 7 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 7 most recent posts we hold, published 25 June 2023 to 4 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.
梦幻西游手游官方最新版本🥴 天天西游不删档内测开启🔥 充值1:500 充值1:500 充值1:500 ✅安卓下载：https://wzw.qingen.fun/apps/i9gr.html ✅苹果下载：https://store-100.appstoregw.cc/92d062eb ✅注册地址：https://xy-1000.ttwan.net/reg?EVKKWP ✅邀请码：EVKKWP 咨询联系 ： 点击此处
梦幻西游手游SF《纵横西游》✅ 充值比例1：1000 打金服 日常挑战均可产出仙玉 🔥 登录即送8技能全红虎啸羊头怪 ✅注册地址： https://zhxy666.xyz/user/reg.php?yqm=ailve ✅双端下载： https://zhxy.yidi.im/ZHXY.html ❣️福利码：可前往聚宝仙子领取 ❣️福利码：纵横西游我爱西游 高级兽诀礼包 x 1高级内丹礼包 x 1金币 x 58888 10000000银币 x 10 福利码：梦幻只玩纵横西游 金币*38888 高级兽诀礼包*1 高级内丹礼包*1 银币*10000000 咨询联系 ： 点击此处
🐱⛔爆爆爆个光，关于逼上的事真的爆不完，爆不完。 大家一起草逼曝光各种套路，还我们一个草逼净土！🤩 爆个逼事📩爆个逼 @baogebi 本店为每个客户提供最好的服务是我们一心追求，同时开通曝光频道，欢迎大家积极投稿，让套路少一点，生活乐趣多一点。 🇦🇩🚗🚕🚙🚌🚎🏎🏎🚓🇦🇼 🔵换汇 租车 外卖 旅游 二手🔵 🍆🍆🥑🥦🥬🥒🫑🌽🌶🌶 24小时在线✅小小乐 @Cebulg 双向联系机器人🎮@FSHFXSBOT 😍点国籍分类查询选择更方便😍 ⭐ 聊天交流🟢⭐ 女孩好评 👍 ⭐ 包月女孩🟢⭐ 驾考宝典 🙂 ⭐ 全球鉴黄🟢⭐ 爆个逼事 🔘
❤2
🔖100%白资🔖(面对面秒到账） 🧷保司法（永久保，一直保） 🧷微信秒到8 🧷支付宝秒到8 🧷面对面转，超过10分钟不到账不收P 🧷大量收u 🧷U换p 🧷U换R —————————————————— 点击关注宿务生活频道不迷路—————————————————— 24小时在线⏰小小乐 @Cebulg 💮宿务地区美女上门修车服务💮 ❣️ 宿务尊享VIP聊天群 ❣️
🔖100%白资🔖(面对面秒到账） 🧷保司法（永久保，一直保） 🧷微信秒到8.1 🧷支付宝秒到8.1 🧷面对面转，超过10分钟不到账不收P 🧷大量收u 🧷U换p 🧷U换R —————————————————— 点击关注宿务生活频道不迷路—————————————————— 24小时在线⏰小小乐 @Cebulg 💮宿务地区美女上门修车服务💮 ❣️ 宿务尊享VIP聊天群 ❣️
👍1🤔1
🔖100%白资🔖(面对面秒到账） 🧷保司法（永久保，一直保） 🧷微信秒到8.2 🧷支付宝秒到8.2 🧷面对面转，超过10分钟不到账不收P 🧷大量收u 🧷U换p 🧷U换R —————————————————— 点击关注宿务生活频道不迷路—————————————————— 24小时在线⏰小小乐 @Cebulg 💮宿务地区美女上门修车服务💮 ❣️ 宿务尊享VIP聊天群 ❣️
Channel created
Showing the 7 most recent of 7 posts we hold for @lefuzf. 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 — 794,027 of 1,565,402entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 4 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.
@lefuzf named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“乐付🍀赌场换汇/代收代付/国内送现” (@lefuzf), 257 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/lefuzf.
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.