Telegram RegisterThe public register of Telegram

Channel

橙子出海-免费投稿骗子曝光

@c69922

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

14,462subscribers

+132 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002310023571
TypeChannel
Username@c69922
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/c69922

Growth

14,32114,46214,391.57 August 2026 — 14,330 subscribers7 August 2026 — 14,330 subscribers8 August 2026 — 14,321 subscribers9 August 2026 — 14,349 subscribers10 August 2026 — 14,377 subscribers11 August 2026 — 14,398 subscribers12 August 2026 — 14,434 subscribers13 August 2026 — 14,462 subscribers7 August 202613 August 2026
8 measurements spanning 6 days, net +132. 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 14,300–14,483 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:5714,462+28
12 Aug 2026, 06:1414,434+36
11 Aug 2026, 08:3214,398+21
10 Aug 2026, 06:2014,377+28
9 Aug 2026, 07:1214,349+28
8 Aug 2026, 05:2014,321-9
7 Aug 2026, 18:0014,330no change
7 Aug 2026, 17:5714,330first reading

Engagement

9 posts held, back to 30 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.01%
avg views ÷ 14,462 subscribers
Avg views / post
725
8 posts measured
Reaction rate
0.214%
reactions ÷ views · ER floor
Posts in window
9
of 9 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. It is computed over the 2 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held9 (30 July 202612 August 2026)
Views total5,796
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 01:57 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
34s
Average length
34s

Measured directly from 1 video 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.

Reaction mix

5 reactions across 1 post, in 1 kind.

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

Measured over the 9 most recent posts we hold, published 30 July 2026 to 12 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

12 Aug 2026, 15:04 UTC222 viewsread 13 August 2026
Photo

📣 新增骗子 ⚠️ 提醒: 担保是唯一安全的交易方式!投稿仅限出海业务 名称:小新同学,多寶 用户名: @Xxtx90211,@duobao08 骗子🆔: 6850197388,6460966067 骗子频道: 无 被骗金额:3523u 交易金额:3523U 事件描述:因为以前合作过的信任,先号后款拖几天后面不打算结算,各大中介号商多多注意 举报人:@feitu8888 举报时间:2026-08-7 21:00 骗子地址:TKDHrNEBpR3ceBEXt2g5StUeWNtP4hWjs6 被骗子关键词:飞机号 举报人: @feitu8888 ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

10 Aug 2026, 05:32 UTC684 viewsread 13 August 2026
Photo

📣 新增骗子 ⚠️ 提醒: 担保是唯一安全的交易方式!投稿仅限出海业务 名称:福音🎵工作室(我只有这个号)其他是骗子 用户名: @fygzs1234 骗子🆔: 7704212306 骗子频道: 无 被骗金额:45u 被骗说明: 8.5号找他购买2个领英号,要先款 ,付完之后就一直不在线,8.8号就退群了。还拉黑了 骗子地址:TKeSsM4DQJNz3iWrxbyHue1wL5RZpJjqAi 被骗子关键词:领英号 举报人: @susu88012 ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

9 Aug 2026, 11:41 UTC665 viewsread 13 August 2026
Photo

📣 新增骗子 ⚠️ 提醒: 担保是唯一安全的交易方式!投稿仅限出海业务 名称:佳佳 短信 ws群发一手 用户名: @yivcc123 骗子🆔: 684565542 骗子频道: 被骗金额:158u 被骗说明: 找他做巴西ws群发图文超链3000条价值158u,给了他台子链接图文,对方说安排当晚发送,结果隔天我后台没数据,之后告诉我发了,连回执都没有,再之后就直接清除记录拉黑我 骗子地址: TD2rjopnG1DUeSx8iehq55jV4U78f9PWrV 被骗子关键词:巴西ws群发图文 举报人: @one016888 ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

7 Aug 2026, 04:22 UTC752 views0 reactionsread 12 August 2026
Photo

😀😀😀😀😀😀 😀😀😀😀😀😀😀 ⚽世界杯官方指定平台 😍开云集团旗下亚洲最顶级娱乐平台 😍体育 H5版 — WEB端入口 😍体育 PC端 — 网页版入口 😍体育 全站APP — APP下载 🔤🔤小程序,免实名-不限IP-U存U取 😍😍😍😍😍😍😀😀😀😀😀😀😀 匿名首选 📱小飞机入口 ⭐首存加赠2⃣5⃣🔣,复存加增1⃣0⃣🔣 ⭐足球/电竞首单包赔1⃣0⃣0⃣🔣 ⭐飞投版MK百家乐享双边返水0⃣🔣9⃣🔣 ❤❤❤❤ @MKFTAF66 ⚡⚡⚡⚡易换支付钱包,1⃣0⃣亿🔤资金池储备 ⚡⚡⚡⚡线上5⃣0⃣0⃣0⃣万🔤担保,拒绝野鸡台 ⚡⚡⚡⚡千万域名,豪客之选 https://mk.bet ❤❤❤❤代理分润 5⃣5⃣🔣 @MKFT888 ❤❤❤❤ @MKFT777 关注🔈😀😀😀😀😀😀😀😀 t.me/rdsjo 掌握东南亚一线动态,看清风向料定先机 频道每周抽取100名TG会员,群发言积分兑🔤

6 Aug 2026, 10:33 UTC763 viewsread 12 August 2026
Photo

名称:富豪【日韩ins th tk手工私信机房】 用户名: @gaoduan0088 骗子🆔: 8123819951 骗子频道: @fuhao686888 被骗金额:59U 被骗说明: 给他上了日本交友粉 拖了十几天都不结账 现在直接不回信息 装死了 骗子地址: 被骗子关键词:日本交友粉 举报人:@aabb03071 (必填,否则举报无效) ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

6 Aug 2026, 09:19 UTC510 viewsread 10 August 2026
Video

😀😀😀😀😀😀 😀😀😀😀😀😀😀 ⚽世界杯官方指定平台 😍开云集团旗下亚洲最顶级娱乐平台 😍体育 H5版 — WEB端入口 😍体育 PC端 — 网页版入口 😍体育 全站APP — APP下载 🔤🔤小程序,免实名-不限IP-U存U取 😍😍😍😍😍😍😀😀😀😀😀😀😀 匿名首选 📱小飞机入口 ⭐首存加赠2⃣5⃣🔣,复存加增1⃣0⃣🔣 ⭐足球/电竞首单包赔1⃣0⃣0⃣🔣 ⭐飞投版MK百家乐享双边返水0⃣🔣9⃣🔣 ❤❤❤❤ https://t.me/MK725826 ⚡⚡⚡⚡易换支付钱包,1⃣0⃣亿🔤资金池储备 ⚡⚡⚡⚡线上5⃣0⃣0⃣0⃣万🔤担保,拒绝野鸡台 ⚡⚡⚡⚡千万域名,豪客之选 https://mk.bet ❤❤❤❤代理分润 5⃣5⃣🔣 @MKFT888 ❤❤❤❤ @MKFT777 关注🔈😀😀😀😀😀😀😀😀 t.me/rdsjo 掌握东南亚一线动态,看清风向料定先机 频道每周抽取100名TG

6 Aug 2026, 06:55 UTC620 viewsread 10 August 2026
Photo

📣 新增骗子 ⚠️ 提醒: 担保是唯一安全的交易方式!投稿仅限出海业务 名称:行者无疆 霖渊 陈霖渊 用户名: @linyuan588 骗子🆔: 8102638389 骗子频道: 被骗金额:2130u 被骗说明: 从6月25号一直拖着现在,天天跟我装着是中介,说那边不给结款,一直都是他在放量,现在用的飞机都是我这边给的,到现在不回信息,这个天天杀熟,一开始都是好好的到后面就不结款了,注意这三个都是同一个人 骗子地址:TAnfmJKPR5hVn9ZtXUdHYEBYJQKK6VqwFA 被骗子关键词: 举报人: @yy102599 (必填,否则举报无效) ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

30 Jul 2026, 07:47 UTC≈1,580 views5 reactionsread 9 August 2026
Photo

名称:为诚:代开会员/兑换TRX! 用户名: @wc789 骗子🆔: 5290465340 骗子频道: wctd.cc @NLTRXBOT @gongqunwc 被骗金额:3000U 被骗说明: 兑换trx钱转过去后 没有到账 联系商家已读消息装死 不给处理 骗子地址:TYjEjT8aR4VXBQHxfNmSehA4BQQQQQQQQQ 被骗子关键词:兑换TRX 能量 举报人: @xiaoxin66669999 ━━━━━━━━━━━━━━ 骗子查询机器人 @pianziAdminbot 曝光申述客服橙享: @c68833

5

Showing the 9 most recent of 9 posts we hold for @c69922. 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 — 631,654 of 1,160,990entries 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 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.

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

“橙子出海-免费投稿骗子曝光” (@c69922), 14,462 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/c69922.

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.