Telegram RegisterThe public register of Telegram
Telegram profile photo for AI, Data Science, Machine Learning & IOT

Channel

AI, Data Science, Machine Learning & IOT

@KDnuggets

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

22,884subscribers

-632 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001105757390
TypeChannel
Username@KDnuggets
CreatedBetween 1 February 2017 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 November 2026
Measurements held68
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/KDnuggets

Topic

Technology — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

22,88423,51623,2006 August 202619 November 2026
68 measurements spanning 105 days, net -632. 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,789–23,611 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 68
Measured (UTC)SubscribersChange
19 Nov 2026, 05:2022,884-10
16 Nov 2026, 06:0922,894-14
12 Nov 2026, 21:0922,908-11
10 Nov 2026, 17:5922,919-10
9 Nov 2026, 02:1122,929-12
7 Nov 2026, 19:4722,941-7
6 Nov 2026, 19:4022,948-6
5 Nov 2026, 20:1022,954-18
4 Nov 2026, 16:3722,972-6
3 Nov 2026, 16:4922,978-8
2 Nov 2026, 18:1922,986-3
1 Nov 2026, 19:4822,989-7
31 Oct 2026, 17:4922,996-6
30 Oct 2026, 20:0923,002-10
29 Oct 2026, 19:2923,012-12
28 Oct 2026, 21:1923,024-4
27 Oct 2026, 20:3623,028-7
26 Oct 2026, 22:2623,035-9
25 Oct 2026, 19:4623,044-6
24 Oct 2026, 17:4423,050first reading

Engagement

47 posts held, back to 26 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 126 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.12%
avg views ÷ 22,884 subscribers
Avg views / post
715
8 posts measured
Reaction rate
0.21%
reactions ÷ views · ER floor
Posts in window
8
of 47 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 10 November 2026
Posts held47 (26 December 2024 – 10 November 2026)
Views total5,720
Reactions total12
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 03:19 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

63 reactions across 31 posts, in 2 distinct kinds. The most used accounts for 98.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6298.4%
👍11.59%

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

Measured over the 47 most recent posts we hold, published 26 December 2024 to 10 November 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

Telegram’s own ‘edited’ marker: 0 of 8 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 08:10 UTC703 views1 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Nov 4–Nov 10, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 💸 TokenEconomizer: Experience-Driven Black-Box Cost Control for Coding Agents Authors/Org: Microsoft Research | arXiv/GitHub: arXiv 2610.22732 / microsoft/TokenEconomizer Bottleneck solved: Cuts the recurring token cost of coding agents across sequential real-world tasks. It prunes irrelevant tools, injects micro-skills, and interrupts fai…

❤1

10 Nov 2026, 08:10 UTC545 views1 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Nov 3–Nov 9, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🔐 DeepMind Agents Find New Cryptographic Attacks on Legacy RSA-1024 Google DeepMind reported on Nov 6 that AI agents, guided by cryptanalysts, found two cryptographic advances against legacy 1024-bit RSA within weeks (modern RSA-2048 is unaffected). Developers and data teams should audit any systems still relying on 1024-bit keys and treat ag…

❤1

3 Nov 2026, 08:10 UTC896 views1 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Oct 27–Nov 3, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🧠 claude-mem: Persistent Memory for AI Coding Agents Authors/Org: thedotmack | GitHub: thedotmack/claude-mem Bottleneck solved: Coding agents lose all context between sessions, forcing developers to re-explain projects every time. It records agent session activity, compresses it with AI, and re-injects the relevant parts at the next sessio…

❤1

2 Nov 2026, 08:10 UTC771 views1 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Oct 27–Nov 2, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🛡️ Google Unveils Gemini 4 Carbon for Cybersecurity and Long-Running Work Google introduced Gemini 4 Carbon on October 28 as its strongest model for security and long-running tasks, scoring 88.2% on SEC-bench Pro (finding vulnerabilities) and 71.0% on CWE-bench (patching them), though it is not yet broadly available. Developers and data team…

❤1

27 Oct 2026, 08:10 UTC966 views2 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Oct 21–Oct 27, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🤖 Harness²: Recursive Agent Harnessing for an Open World Authors/Org: Google (Google Research) | arXiv/GitHub: arXiv 2610.14224 · google-research/harness2 Bottleneck solved: Accuracy — agent execution harnesses are hand-tuned and need ground-truth verifiers to improve. It refines harnesses recursively at the task level and learns continua…

❤2

27 Oct 2026, 08:10 UTC717 views2 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Oct 20–Oct 26, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🧮 A Fix for Softmax and Cross-Entropy Authors/Org: Jonathan T. Barron, Dan Gnanapragasam, Michael Tschannen | arXiv: 2610.31642 Bottleneck solved: Accuracy and training stability, by fixing two numerical bugs in standard softmax, log-softmax and cross-entropy that cause gradient collapse and cancellation errors at extreme logit values. Pr…

❤2

27 Oct 2026, 08:10 UTC541 views2 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Oct 20–Oct 26, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 💻 Nanbeige4.3-33B: Open-Weights Coding Model Under Apache 2.0 BOSS Zhipin's Nanbeige LLM Lab released Nanbeige4.3-33B, an open-weights coding model under the permissive Apache 2.0 license. Developers can self-host it for code generation and review without per-token API costs, and data teams can fine-tune it on internal codebases. 🔗 Nanbeige…

❤2

27 Oct 2026, 08:10 UTC581 views2 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Oct 12–Oct 19, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🎙️ xAI Launches Grok Voice 3.0 xAI released Grok Voice 3.0 on October 14, a speech-to-speech model optimized for high-volume conversational calls. Developers can use it to build voice agents for support and call-automation workflows, and data teams can mine the resulting call transcripts for analytics. 🔗 xAI Launches Grok Voice 3.0 for High…

❤2

13 Oct 2026, 08:10 UTC≈1,300 views3 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Oct 7–Oct 13, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🎬 DiffusionART: Efficient, Stable and Scalable RL for Diffusion Models Authors/Org: Zhenglin Wan, Jiayu Chen, Zhengfeiyang Zhang (KlingAI Research) | arXiv/GitHub: arXiv 2610.12572 Bottleneck solved: Cost and instability of online RL fine-tuning for image/video diffusion models, with up to 12x fewer GPU hours than DiffusionNFT and Flow-GRP…

❤3

12 Oct 2026, 08:10 UTC≈1,170 views4 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Oct 5–Oct 12, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. ⚡ Claude Haiku 5.5 Slashes Small-Model Costs Anthropic launched Claude Haiku 5.5, its smallest model, priced at $0.10 input / $0.50 output per million tokens with new effort controls and a reported 72.4% on OSWorld 2.1 computer-use tasks. Developers and data teams can run high-volume agent, classification, and extraction pipelines far more c…

❤3👍1

9 Oct 2026, 08:10 UTC≈1,180 views2 reactionsread 19 November 2026

🔬 AI Research Digest 📅 Week of Oct 3–Oct 9, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🤖 Long-WAM: Scaling the Context of World-Action Models Authors/Org: Wei Huang, Bohan Zhang, Chenzhi Liu (NVIDIA / MIT / HKU / UCSD) | arXiv/GitHub: 2610.10528 Bottleneck solved: Speed vs. memory in real-time robot control — longer visual histories only pay off when the video backbone is pretrained autoregressively, and Long-WAM keeps that h…

❤2

9 Oct 2026, 08:10 UTC≈1,000 views1 reactionsread 19 November 2026

🤖 AI Weekly Digest 📅 Week of Oct 3–Oct 9, 2026 ━━━━━━━━━━━━━━━━━━━━━━━━ 1. 🚀 OpenAI Rolls Out GPT-6 with "Intelligent UI" OpenAI began rolling out GPT-6, which renders tappable buttons, custom calculators, and editable graphs inline instead of plain text, with Pro, Plus, Business, and Enterprise users getting access first and free tiers following via GPT-6 Luna. For developers and data teams, this signals a shift fr…

❤1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 2 registered channels — 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 19 November 2026 — this entry's latest reading, not the date you are reading this.

“AI, Data Science, Machine Learning & IOT” (@KDnuggets), 22,884 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/KDnuggets.

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.