Telegram RegisterThe public register of Telegram
Telegram profile photo for 150u/条【橙子供需】

Channel

150u/条【橙子供需】

@c69911

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

57,019subscribers

-1,732 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002353429701
TypeChannel
Username@c69911
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 live20 October 2026
Measurements held44
Confirmed unchanged1 time, most recently 20 October 2026
On Telegramt.me/c69911

Topic

Marketing & affiliate — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.

Growth

56,89961,46359,1817 August 2026 — 58,751 subscribers7 August 2026 — 58,751 subscribers8 August 2026 — 58,716 subscribers9 August 2026 — 58,774 subscribers10 August 2026 — 58,870 subscribers11 August 2026 — 58,839 subscribers12 August 2026 — 58,962 subscribers13 August 2026 — 59,004 subscribers15 August 2026 — 59,102 subscribers16 August 2026 — 59,071 subscribers17 August 2026 — 59,032 subscribers18 August 2026 — 59,003 subscribers19 August 2026 — 59,178 subscribers20 August 2026 — 59,231 subscribers21 August 2026 — 59,340 subscribers23 August 2026 — 59,457 subscribers24 August 2026 — 59,607 subscribers25 August 2026 — 59,633 subscribers26 August 2026 — 59,661 subscribers27 August 2026 — 59,775 subscribers29 August 2026 — 59,886 subscribers29 August 2026 — 59,979 subscribers30 August 2026 — 60,082 subscribers31 August 2026 — 60,159 subscribers1 September 2026 — 60,186 subscribers2 September 2026 — 60,229 subscribers4 September 2026 — 60,309 subscribers6 September 2026 — 60,398 subscribers9 September 2026 — 60,520 subscribers12 September 2026 — 60,544 subscribers13 September 2026 — 60,595 subscribers15 September 2026 — 60,695 subscribers17 September 2026 — 60,947 subscribers19 September 2026 — 61,280 subscribers26 September 2026 — 61,463 subscribers4 October 2026 — 61,302 subscribers9 October 2026 — 58,367 subscribers13 October 2026 — 56,931 subscribers14 October 2026 — 56,930 subscribers15 October 2026 — 56,915 subscribers16 October 2026 — 56,899 subscribers17 October 2026 — 56,955 subscribers18 October 2026 — 56,980 subscribers20 October 2026 — 57,019 subscribers57,0197 August 202620 October 2026
44 measurements spanning 73 days, net -1,732. 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 56,214–62,148 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 44
Measured (UTC)SubscribersChange
20 Oct 2026, 01:0057,019+39
18 Oct 2026, 22:0656,980+25
17 Oct 2026, 19:1756,955+56
16 Oct 2026, 19:4756,899-16
15 Oct 2026, 20:5856,915-15
14 Oct 2026, 19:0956,930-1
13 Oct 2026, 08:2056,931-1,436
9 Oct 2026, 01:5958,367-2,935
4 Oct 2026, 17:1761,302-161
26 Sept 2026, 15:3861,463+183
19 Sept 2026, 17:3961,280+333
17 Sept 2026, 06:3860,947+252
15 Sept 2026, 08:2160,695+100
13 Sept 2026, 19:4160,595+51
12 Sept 2026, 02:0060,544+24
9 Sept 2026, 20:5460,520+122
6 Sept 2026, 15:3660,398+89
4 Sept 2026, 06:1660,309+80
2 Sept 2026, 17:0760,229+43
1 Sept 2026, 16:5760,186first reading

Engagement

231 posts held, back to 29 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 148 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.53%
avg views ÷ 57,019 subscribers
Avg views / post
873
89 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
90
of 231 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 19 October 2026
Posts held231 (29 July 2026 – 19 October 2026)
Views total77,710
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Oct 2026, 19:29 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.

Recent posts

19 Oct 2026, 12:30 UTC526 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:财神海外数据|全球源头数据 自有技术团队|一手源头直出 覆盖全球多国 多行业数据 TG / WS / LINE / ZALO 等 支持国家 行业 平台定向筛选 现筛现跑 按需求定制 长期稳定供货 拒绝多层转手 量大价优 支持代理合作 📱 联系方式:@So15998 🤖 双向机器: 🏷 商品频道:@So156688 🛡 交易方式:支持橙子担保 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

19 Oct 2026, 03:00 UTC738 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:蝴蝶代投 打粉&代投TK / FB 纯广告粉 ✅ 主营业务:兼职/多肽/游戏/空降/网赚等不限上述提及业务 ✅ 全球能接,现成资源可直接上量 ✅ 稳定日供上大几千量,欢迎长期绑定 📱 联系方式:@hudie99 🤖 双向机器: 🏷 商品频道:@hudie888888888 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

18 Oct 2026, 12:30 UTC832 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:财神海外数据|全球源头数据 自有技术团队|一手源头直出 覆盖全球多国 多行业数据 TG / WS / LINE / ZALO 等 支持国家 行业 平台定向筛选 现筛现跑 按需求定制 长期稳定供货 拒绝多层转手 量大价优 支持代理合作 📱 联系方式:@So15998 🤖 双向机器: 🏷 商品频道:@So156688 🛡 交易方式:支持橙子担保 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

18 Oct 2026, 06:00 UTC820 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:海拓广告TK / FB / GG 三大平台 源头户商 1️⃣tk老户,加白户,不限行业,不限地区 2️⃣谷歌老百破限户 3️⃣谷歌白户,老户,各种业务 4️⃣FB二,三不限,嘎嘎起量,下户快 📱 联系方式:@xian9hu 🤖 双向机器: 🏷 商品频道:@Ads_bibi 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

17 Oct 2026, 12:30 UTC922 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:财神海外数据|全球源头数据 自有技术团队|一手源头直出 覆盖全球多国 多行业数据 TG / WS / LINE / ZALO 等 支持国家 行业 平台定向筛选 现筛现跑 按需求定制 长期稳定供货 拒绝多层转手 量大价优 支持代理合作 📱 联系方式:@So15998 🤖 双向机器: 🏷 商品频道:@So156688 🛡 交易方式:支持橙子担保 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

17 Oct 2026, 03:00 UTC≈1,010 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:蝴蝶代投 打粉&代投TK / FB 纯广告粉 ✅ 主营业务:兼职/多肽/游戏/空降/网赚等不限上述提及业务 ✅ 全球能接,现成资源可直接上量 ✅ 稳定日供上大几千量,欢迎长期绑定 📱 联系方式:@hudie99 🤖 双向机器: 🏷 商品频道:@hudie888888888 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

16 Oct 2026, 14:49 UTC689 viewsread 19 October 2026

橙子技术原生开发|全网骗子一键查询: @pianziAdminbot 😎 身份介绍: 橙子会员 🔔 需求信息: 收台空降色粉,手工 二筛 落地页 全部一律都要 💼 合作要求: 📱 联系方式:@Jiangz8 🤖 双向机器: 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

16 Oct 2026, 12:30 UTC861 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:财神海外数据|全球源头数据 自有技术团队|一手源头直出 覆盖全球多国 多行业数据 TG / WS / LINE / ZALO 等 支持国家 行业 平台定向筛选 现筛现跑 按需求定制 长期稳定供货 拒绝多层转手 量大价优 支持代理合作 📱 联系方式:@So15998 🤖 双向机器: 🏷 商品频道:@So156688 🛡 交易方式:支持橙子担保 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

16 Oct 2026, 11:50 UTC558 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:精准劫持渗透数据 商品:精准劫持渗透数据 精聊 股民 兼职 刷单 精聊 股民 兼职 刷单 精聊 股民 兼职 刷单 精聊 股民 兼职 刷单 公司自有,全球热门国家,出粉库,拿料可过 📱 联系方式:@HULV1 🤖 双向机器: 🏷 商品频道:@HULV11 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

16 Oct 2026, 07:15 UTC871 viewsread 19 October 2026

橙子技术原生开发|全网骗子一键查询: @pianziAdminbot 😎 身份介绍: 橙子用户 🔔 需求信息: 收 日本企业line 满七天的 💼 合作要求: 📱 联系方式:@XBnltrxx1 🤖 双向机器: 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

16 Oct 2026, 06:00 UTC889 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:海拓广告TK / FB / GG 三大平台 源头户商 1️⃣tk老户,加白户,不限行业,不限地区 2️⃣谷歌老百破限户 3️⃣谷歌白户,老户,各种业务 4️⃣FB二,三不限,嘎嘎起量,下户快 📱 联系方式:@xian9hu 🤖 双向机器: 🏷 商品频道:@Ads_bibi 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

15 Oct 2026, 12:30 UTC961 viewsread 19 October 2026

全网骗子一键查询 @pianziAdminbot ⬇️ 😎 身份介绍:橙子会员👑 🖥 供应信息:财神海外数据|全球源头数据 自有技术团队|一手源头直出 覆盖全球多国 多行业数据 TG / WS / LINE / ZALO 等 支持国家 行业 平台定向筛选 现筛现跑 按需求定制 长期稳定供货 拒绝多层转手 量大价优 支持代理合作 📱 联系方式:@So15998 🤖 双向机器: 🏷 商品频道:@So156688 🛡 交易方式:支持橙子担保 🛡 交易方式:支持橙子担保 🔰 担保是唯一安全交易方式! 发现欺诈请联系 @c65588bot

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

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

“150u/条【橙子供需】” (@c69911), 57,019 subscribers as measured 20 October 2026. Telegram Register, tgregister.com/channel/c69911.

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.