Telegram RegisterThe public register of Telegram
Telegram profile photo for 少儿编程启蒙 K12 教育数据

Channel

少儿编程启蒙 K12 教育数据

@Alidatas

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

23subscribers

+1 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002117524117
TypeChannel
Username@Alidatas
CreatedBetween 1 November 2023 and 5 December 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live2 October 2026
Measurements held5
Confirmed unchanged3 times, most recently 2 October 2026
On Telegramt.me/Alidatas

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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

22242314 August 2026 — 22 subscribers14 August 2026 — 22 subscribers23 August 2026 — 23 subscribers31 August 2026 — 24 subscribers9 September 2026 — 23 subscribers14 August 20269 September 2026
5 measurements spanning 26 days, net +1. 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 22–24 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 05:5923-1
31 Aug 2026, 15:5424+1
23 Aug 2026, 15:4523+1
14 Aug 2026, 16:1522no change
14 Aug 2026, 16:0222first reading

Engagement

13 posts held, back to 5 December 2023 — 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 page of 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 13 posts for this entry, the most recent from 4 April 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 1 kind.

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

Measured over the 13 most recent posts we hold, published 5 December 2023 to 4 April 2024, 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

4 Apr 2024, 07:44 UTC726 viewsread 14 August 2026

收单收量,客户复购率最高的通道,7点截止。 昨天下单的稍等,马上分包🤝🏻

2 Apr 2024, 06:14 UTC725 viewsread 14 August 2026

APP注册活跃-规则: 条数:3000条起 (降低门槛) 时间:当天6点提单,T1出数 行业:全行业 有App就可以 区域:可指定城市 运营商:不指定 统一三网 精准率:75-80% 建议提小众App,质量比大众App质量要好。 @lbdashuju

10 Mar 2024, 15:44 UTC934 views1 reactionsread 14 August 2026

最近很少发动态,不过数据一直再出,需要的客户直接发需求模型过来就可以了。 目前只做:SDK DPI 短信提取 Q微提取,不做其他的,判断一个人专不专业就看他做的种类,如果什么都想掺一手,那他做的不一定深入,我们一直深耕数据提取,数据质量不用客户说,团队也会把控,一直坚信数据只要好,客户不会少,需要数据的客户请联系 @laobai2021

❤1

10 Mar 2024, 15:42 UTC864 viewsread 14 August 2026

新签Talking Data产品,提取App活跃用户,比市面Sdk 网提质量要好,现在收量,有量的客户来合作,给成本价,目前仅限白色,灰色等通知,灰色可跑三网DPI @laobai2021

8 Mar 2024, 09:40 UTC726 viewsread 14 August 2026

新签Talking Data产品,提取App活跃用户,比市面Sdk 网提质量要好,现在收量,有量的客户来合作,给成本价,目前仅限白色,灰色等通知,灰色可跑三网DPI @laobai2021

16 Jan 2024, 04:48 UTC649 viewsread 14 August 2026

老板们,昨天移动移动集团没下发数据到省里,数据今晚出。

6 Jan 2024, 09:40 UTC612 viewsread 14 August 2026
Forwarded from @lbdashujuPhoto

少儿编程目前新dpi和TD sdk通道反馈不错,有客户做少儿编程的,速来,模型很多。 目前全行业模型可跑,老白办事,你放心,源头直签运营商。合作 @laobai2021

4 Jan 2024, 11:22 UTC503 views1 reactionsread 14 August 2026

目前经营产品: 1-移动DPI 渠道直签,非市面垃圾通道,目前跑出数据非常优质,灰色可夹带着跑,每周一提单周三出,后续每天可出。 2-TD SDK 极光SDK 极光大家都不陌生,TD是新通道,目前跑贷款反馈不错,有量有价,T2出数。 目前深耕运营商数据,专业性不用担心,源头直签。 另外不做乱七八糟的要素数据,不要上来就说渗透提权,这种说能做的不能说百分百骗子,但是真正有水平的也不会出来接单。 只做能力范围内的事,数据提取就找老白。 @laobai2021

❤1

17 Dec 2023, 13:23 UTC482 viewsread 14 August 2026
File

下单格式: 数量:10000 地区:全国 运营商:三网 平台:洋钱罐借款 你我贷借款 关键词: 时效: 老板们,短信的这样下单发给我。

17 Dec 2023, 13:22 UTC451 viewsread 14 August 2026
Photo

标签新接口,全行业支持啦‼️ 最新APP标签数据接口,真实注册用户资源,精准来源 数据真实对库率高达90%以上 更新逻辑跟以前的短信标签点对点提权一样,一周2次大库,全新大库没被洗过 经多个行业客户验证数据质量真实可靠 【APP网提标签】质量秒杀 MD5 男女sdk app下拉 等类产品 单个APP 5000条起提,可筛选地区,去重复规则(单个APP自然月去重复)

16 Dec 2023, 10:15 UTC481 viewsread 14 August 2026
Photo

体育,教育,白酒,装修,人力资源,医美 等覆盖全行业 1网提,近期效果非常不错 2DPI (联通,移动)正规,全行业日活跃用户推广,适合电销。 3:短信(又名验证数据,)提供短信验证码模板,获取的就是收到短信模板的用户,适用于体育股票 白酒等全行业! @laobai2021

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“少儿编程启蒙 K12 教育数据” (@Alidatas), 23 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Alidatas.

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.