Telegram RegisterThe public register of Telegram
Telegram profile photo for 大唐科技出货频道

Channel

大唐科技出货频道

@datangkeji3366

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

11,186subscribers

-1,078 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002009308528
TypeChannel
Username@datangkeji3366
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live30 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/datangkeji3366

Growth

9,91812,26411,09114 August 2026 — 12,264 subscribers15 August 2026 — 11,555 subscribers16 August 2026 — 9,918 subscribers19 August 2026 — 11,617 subscribers20 August 2026 — 11,536 subscribers22 August 2026 — 11,490 subscribers23 August 2026 — 11,456 subscribers25 August 2026 — 11,368 subscribers25 August 2026 — 11,322 subscribers26 August 2026 — 11,310 subscribers28 August 2026 — 11,279 subscribers28 August 2026 — 11,242 subscribers29 August 2026 — 11,199 subscribers30 August 2026 — 11,186 subscribers11,18614 August 202630 August 2026
14 measurements spanning 17 days, net -1,078. 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 9,566–12,616 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 15:1311,186-13
29 Aug 2026, 18:4511,199-43
28 Aug 2026, 21:2511,242-37
28 Aug 2026, 00:3411,279-31
26 Aug 2026, 22:0311,310-12
25 Aug 2026, 23:5311,322-46
25 Aug 2026, 00:2811,368-88
23 Aug 2026, 15:2711,456-34
22 Aug 2026, 04:5811,490-46
20 Aug 2026, 18:0411,536-81
19 Aug 2026, 20:2811,617+1,699
16 Aug 2026, 19:489,918-1,637
15 Aug 2026, 07:2611,555-709
14 Aug 2026, 00:3112,264first reading

Engagement

39 posts held, back to 27 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 23 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.7%
avg views ÷ 11,186 subscribers
Avg views / post
1,200
31 posts measured
Reaction rate
0.182%
reactions ÷ views · ER floor
Posts in window
31
of 39 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 31 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 28 August 2026
Posts held39 (27 July 202628 August 2026)
Views total37,062
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 10:18 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.

Reaction mix

8 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
562.5%
👍112.5%
😁112.5%
🥰112.5%

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 39 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 39 most recent posts we hold, published 27 July 2026 to 28 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

28 Aug 2026, 06:36 UTC≈1,070 viewsread 29 August 2026

📱kakao成品号带好友,开通1;1聊天,价格不便宜,带热门需要的滴滴

27 Aug 2026, 12:18 UTC≈1,190 viewsread 29 August 2026

📱IG 日本大黑 台湾大小黑 到货 要的老板抓紧数量不多

27 Aug 2026, 04:40 UTC≈1,070 views3 reactionsread 29 August 2026

✈️飞机号系列 ✈️飞机号双向解除技术,收费告知!!!让你随时一个号私聊上百人!!! Telegram账号|✈️随机国家精养飞机号15米 🔥 Telegram账号|🇳🇱+299格陵兰岛|短位靓号| Telegram账号|🇨🇴+57哥伦比亚| Telegram账号|🇳🇬+234尼日利亚| Telegram账号|🇨🇮+225科特迪瓦| Telegram账号|🇪🇹+251埃塞俄比亚| Telegram账号|🇨🇩+243刚果| Telegram账号|🇹🇩+235乍得| Telegram账号|🇹🇿+255坦桑尼亚| Telegram账号|🇪🇬+20埃及| Telegram账号|🇱🇾+218利比亚| Telegram账号|🇸🇱+232塞拉利昂| Telegram账号|🇿🇲+260赞比亚| Telegram账号|🇧🇯+229贝宁| Telegram账号|🇿🇼+263津巴布韦| Telegram账号| 🇩🇿+213莫阿尔及利亚| Telegr

1👍1😁1

26 Aug 2026, 10:17 UTC≈1,080 viewsread 29 August 2026
Photo

✅静态ip【独享养号防封】 SOCKS5,HTTP,VMESS,L2TP,SS协议等均可定制... 支持:苹果端,安卓端,Windows,IOS,指纹浏览器ADS.比特浏览器,软路由等... 用途:📱FaceBook、📱Tiktok、📱instagram,📱Whats APP、📱LINE 、巴豆,大黄蜂,📱火种,📱微信,📱QQ,📱抖音,快手等养号以及引流用途 目前已上线 中国、美国 、日本、英国、越南、台湾、香港、韩国、印度、德国、西班牙、英国、荷兰、马来西亚、新加坡、菲律宾、印尼、泰国、阿拉伯联合酋长国、墨西哥等全球地区的家庭住宅静态I

25 Aug 2026, 07:26 UTC≈1,210 viewsread 29 August 2026

📱Facebook美国真人耐用 美国本土原生态 老白号 0-29好友-2007-2024年份 已开启2FA 带邮箱(单邮箱)UID 1000开头 78 📱FB—美国耐用-本土老号-30-1000好友-注册2009-2024~单邮箱~双重登入-带邮箱密码(可改名字) 148r 📱FB-美国耐用-本土老号-好友30-5000-2007-2024年份-已开启2FA-带微软邮箱 100r 📱FB--美国本土真人老号----随机好友-----双重登入-----2007-2025年份--带邮箱密码----包24首登 68r 📱Facebook美国超级老号--本土老号--已开启2fa-带邮箱密码--2018年之前--性别女 85r 📱Facebook美国耐用-本土老号-2000以上好友-2007-2024年份 196r 📱Facebook美国耐用-本土老号-500以上好友-2007-2024年份 166r 📱Facebook美国

22 Aug 2026, 06:23 UTC≈1,170 viewsread 29 August 2026

香港📱🇭🇰6-12月绑visa卡 国外私人换绑 不能收付 已过验证 可加人接粉 进群 国外网络无视或香港网 硬邦邦‼️现货秒发 香港🇭🇰1-7天短信上 香港🇭🇰8-15天短信上 香港🇭🇰半年短信上 香港🇭🇰年号短信上 香港🇭🇰3-5年短信上 香港🇭🇰3-5年假护照短信上 香港🇭🇰3-5年通行证 🉑进企业 香港🇭🇰3-5年视频号 🉑发作品

21 Aug 2026, 08:11 UTC≈1,120 viewsread 29 August 2026

📱美国fb大小黑包pay 大已到货 📱韩国ins大小黑到货

21 Aug 2026, 07:19 UTC≈1,130 viewsread 29 August 2026

1️⃣接📱快手首码,成品老号一码直登带链接 2️⃣接📱陌陌首码,成品老号一码直登带链接 3️⃣接🌟灵魂首码,成品老号一码直登带链接 4️⃣接🌟探探首码,成品老号预定 5️⃣接📱小红书首码,成品老号一码直登带链接

20 Aug 2026, 04:25 UTC≈1,130 views1 reactionsread 29 August 2026
Photo

😳1.line(赖)台湾,泰国,韩国,日本认证,可留卡复 😳2.WhatApp(WS)各国新号,老号,可留卡复接 📱3.香港/美国VCC信用卡可订阅会员充值商品消费 😀4.apple(苹果)各国 iTunes充值礼品卡,AppleID 苹果账号 😀5.Telegram(飞机)各国精养老号,协议号,直登号【官网直开会员,价格低操作快】 😀6.AI机器人ChatGPT账号,代开会员plus功能月15u 😀7.Facebook(FB脸书)有缘,冲锋号,老号,帖子号,粉丝号,自选号 😀8.Instagram(IG)新号,老号,帖子号,粉丝号,自选号,带脆Threads 😀9.各国本土真人Twitter(推特X)小白号,老号,粉丝号 😳10.TikTok(海外抖音权重号)小白号,老号,粉丝号 😳11.Youtube(油管)老号、真人粉丝、浏览关注等套餐服务 😀😀😀😀😀😀😀😀😀😀😀😀 😀【全球IP节点】【ads指纹游览器兑换码【大黄蜂Bum

1

18 Aug 2026, 15:06 UTC≈1,240 viewsread 29 August 2026

谷歌邮箱系列 📱【新号】全新注册随机谷歌账号 (注册2-3天) 12R 📱【新号】全新美国谷歌账号(注册2-3天,美国注册) 17R 📱【新号】稳定全新Gmail账号(注册时间10-15天左右) 18R 📱【优质】2fa满3个月个人谷歌Gmail邮箱(有gcp但不包,链接可用7天.有使用痕迹) 16R 📱【优质】2020-2025年个人谷歌Gmail邮箱不包谷歌云(有2fa,有使用痕迹)17R 📱【2fa优质】满年个人谷歌Gmail邮箱(高质量,有使用痕迹) 15R 📱{优质】5年以上老号(轻微使用痕迹,有谷歌云,但不包)25R 📱【美国】美国谷歌邮箱老号(满3年.链接可用7天·有使用痕迹) 20R 📱【美国】2020-2024注册美国谷歌Gmail邮箱(有2fa,不包谷歌云,有使用痕迹) 21R 📱【老号】2010-2023年随机注册个人谷歌邮箱(有2fa,有使用痕迹) 28R 📱【油管】 YouTube 频道已创建 部分有

Showing the 12 most recent of 39 posts we hold for @datangkeji3366. 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 — 1,143,007 of 1,628,524entries 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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“大唐科技出货频道” (@datangkeji3366), 11,186 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/datangkeji3366.

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.