Telegram RegisterThe public register of Telegram

Channel

【喜茶供需】小白网赚灰产项目资源

@u2230

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

47,407subscribers

-664 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-1002855496767
TypeChannel
Username@u2230
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/u2230

Growth

47,40748,07147,7397 August 2026 — 48,071 subscribers8 August 2026 — 48,010 subscribers9 August 2026 — 47,925 subscribers10 August 2026 — 47,831 subscribers11 August 2026 — 47,602 subscribers12 August 2026 — 47,514 subscribers13 August 2026 — 47,407 subscribers7 August 202613 August 2026
7 measurements spanning 6 days, net -664. 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 47,307–48,171 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 10:2647,407-107
12 Aug 2026, 10:1447,514-88
11 Aug 2026, 08:2647,602-229
10 Aug 2026, 08:5047,831-94
9 Aug 2026, 10:5147,925-85
8 Aug 2026, 13:1048,010-61
7 Aug 2026, 15:0148,071first reading

Engagement

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

ERR · 30 days
13.1%
avg views ÷ 47,407 subscribers
Avg views / post
6,200
32 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
32
of 32 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 13 August 2026
Posts held32 (3 August 202613 August 2026)
Views total198,367
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 08: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.

What this channel posts

Video runtime
5m 03s
Average length
51s

Measured directly from 6 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

13 Aug 2026, 07:59 UTC3 viewsread 13 August 2026

业务名称:线下做事运货 业务介绍:线下做事 3天到手10w+(稳定安全可以预付) 主要招人线下做事 二,要求 年龄18-35 身体素质过硬 无残疾 有眼色 可爬山 听组织安排 面对突发情况有一定的反应能力 三,结算方式 一趟8-15万人民币/报销车旅费用/结账百分之50 剩余送达付款(全程公群报备) 欢迎各大实力中介合作 茶水丰厚 对接人:@paig789 了解热线:https://t.me/+O8WO2OiY0o8zZmJl

13 Aug 2026, 04:08 UTC136 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

12 Aug 2026, 10:37 UTC≈3,150 viewsread 13 August 2026

需 需求类型: 二叔团队招知情仁头,不限男女,25岁以上 (有技术开微信牛户) 微信牛户,仁头6个点!多种变现方式轮流压榨!200万_400万量拉满!日结秒回u!包来回飞机票,吃住全包! 对接方式对接人:助理二叔:@jinbi88888

12 Aug 2026, 04:08 UTC≈5,840 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

11 Aug 2026, 14:34 UTC≈3,720 viewsread 13 August 2026

提供类型:8G国际娱乐电子 体育 视讯 投注U台 TG最热门综合U台,上千款游戏/H66666公群 /新老客户充值领取TRX,上下分手续费无忧 1.新用户注册符合条件送18U-38U 2.平台福利多多:活动救援金、返佣金、充值金、闯关奖、摇骰子奖、充值额外奖、周福利、月福利等等 3.频道每日5个红包/平台18个高爆率活动/视讯8输9转运金,连胜连败加奖/充值加奖 4:视讯双边1%高反水,输赢都返,体育反水0.85,PC28高额反水,输赢双边计算 5.顶级域名,千万价值,大额无忧 限红比肩任何平台 大胆来玩 欢迎来爆庄 对接人: @KF8G

11 Aug 2026, 04:08 UTC66 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

10 Aug 2026, 09:58 UTC≈5,340 viewsread 13 August 2026

提供类型:唐人白资收U 项目介绍:团队20亿业绩,价格美丽,大额无忧,欢迎各位新老客户光临对接,白资港湾,包永久。 新增模式:大额KK 抖音币 虎牙币代充。欢迎咨询 (全网各大担保都有上压)总计上压76万U 价格:每天价格置顶 对接人:@trj888

10 Aug 2026, 04:08 UTC≈49,100 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

9 Aug 2026, 12:52 UTC≈11,100 viewsread 13 August 2026

提供类型:p各种资料,专业切客记录,视频换脸,对口型,克隆声音 优 势:设计头像 p图 公章 证件 合同 聊天记录 专业切客视频 各种视频制作修改以及定制服务 对接方式/对接人:@ps11777

9 Aug 2026, 12:52 UTC≈1,950 viewsread 13 August 2026

需求类型: 金鑫诚招:全国拿现车(找车队合作,一手直盘精聊前中期!不做尾叨!料多!料稳!全国派单!车对属于U商,0风险) 此模式上线两年,没有出现过一次按投的情况,无本金的勿扰,黑中介,AB微信,滚远点 优 势: 上浮1快起,日量1000+ 招收微信支付宝车队 对接方式/对接人: @xxxxoooo

9 Aug 2026, 04:08 UTC70 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

8 Aug 2026, 04:08 UTC≈1,500 viewsread 13 August 2026
Photo

🔥 海外华人 & 留学生必备神器 ✅ 豆豆加速器|一键回国专线,稳定低延迟 🎬 海外畅享国内视频、音乐、直播,解锁地区限制 🎮 国服手游超低延迟,不卡顿、不掉线、稳定畅玩 🔒 专线加密传输,隐私安全有保障,多设备通用 😀 下载直达: ddjsq.vip/v163 😀新用户免费试用,晚高峰依旧丝滑流畅 😀在海外追剧、听歌、打游戏,有它就够了!

Showing the 12 most recent of 32 posts we hold for @u2230. 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 — 530,421 of 1,176,251entries 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.

“【喜茶供需】小白网赚灰产项目资源” (@u2230), 47,407 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/u2230.

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.