电信DPI也支持目前,不支持移动DPI
Signed 红SDK 数据

Channel
@redshuju1
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
59subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001634225100 |
|---|---|
| Type | Channel |
| Username | @redshuju1 |
| Created | Between 1 December 2021 and 27 June 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 2 times, most recently 17 August 2026 |
| On Telegram | t.me/redshuju1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:17 | 59 | no change |
| 11 Aug 2026, 08:48 | 59 | first reading |
20 posts held, back to 27 June 2022 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 14 December 2022. An engagement rate over an empty window would be a number about nothing.
电信DPI也支持目前,不支持移动DPI
Signed 红SDK 数据
联通DPI (带连接)已正式恢复!有需要提单的客户抓紧整理模型发上来
Signed 红SDK 数据
今日已开工,联通dpi;三网dpi;sdk欢迎咨询
Signed 红SDK 数据
国庆正常在线,可以直接消息咨询 sdk或者dpi
Signed 红SDK 数据
新数据产品上线 微博指定文章链接抓取活跃互动用户数据,抓取博主粉丝数据,只能抓微博, 每天下午五点前安排,次日下午出数据,起定2000条。
Signed 红SDK 数据
这些可以,别的行业。有马扁的都不行。
Signed 红SDK 数据
教育 游戏 房地产 汽车 保险 婚纱 家装 驾校
Signed 红SDK 数据
独家渠道,白行短信裸号,价格感人。欢迎来咨询。只限白行。
Signed 红SDK 数据
sdk dpi 短信标签 👉联系技术✈️@redshuju
Signed 红SDK 数据
频道日常在线.。。最近确实很忙
Signed 红SDK 数据
短信标签目前恢复出裸号的
Signed 红SDK 数据
实在抱歉,在分发数据。这两天有点事情耽误了
Signed 红SDK 数据
Showing the 12 most recent of 20 posts we hold for @redshuju1. 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 — 1,290,228 of 1,480,975entries 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.
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.
@redshuju1 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“🎖红数据🎖免费‼️运营商三网SDK数据一级代理” (@redshuju1), 59 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/redshuju1.
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.