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 16 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
13 measurements spanning 38 days, net -24. 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 2,204–2,239 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Sept 2026, 17:00
2,208
-7
9 Sept 2026, 13:01
2,215
-1
4 Sept 2026, 07:15
2,216
+3
1 Sept 2026, 00:38
2,213
+1
28 Aug 2026, 23:08
2,212
+4
25 Aug 2026, 12:45
2,208
-12
22 Aug 2026, 04:47
2,220
+5
18 Aug 2026, 21:56
2,215
-19
16 Aug 2026, 06:25
2,234
+4
12 Aug 2026, 15:17
2,230
-5
9 Aug 2026, 23:32
2,235
+2
6 Aug 2026, 23:35
2,233
+1
6 Aug 2026, 16:06
2,232
first reading
Engagement
20 posts held, back to 12 October 2016 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 20 posts for this entry, the most recent from 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
60 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 31.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
19
31.7%
❤
16
26.7%
👍
13
21.7%
👏
9
15.0%
👎
2
3.33%
🥰
1
1.67%
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 5 of the 20 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 60 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 October 2016 to 14 July 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.
🚀 node-telegram-bot-api v1.2.0 is out - with Bot API 10.2 support!
👻 Ephemeral Messages: send group messages only one user can see:
bot.sendMessage(chatId, "hi", { receiver_user_id: userId })
Plus new methods to manage them: editEphemeralMessageText, editEphemeralMessageMedia, editEphemeralMessageCaption, editEphemeralMessageReplyMarkup and deleteEphemeralMessage.
📝 Rich Messages: new block-based formatting via Inp…
🛠 node-telegram-bot-api v1.1.2 is out - CommonJS support
📦 Dual ESM + CommonJS build
• ESM imports keep working unchanged
• CommonJS can now use require() again
• ships matching .d.ts / .d.cts typings
🗺 Source maps
• emitted for both ✨ ESM and CJS builds
📦 npm i [email protected]
📝 Changelog: v1.1.2
🛠 node-telegram-bot-api v1.1.1 is out - focused fixes for proxies, media edits, and stickers!
🌐 Per-bot custom transport
• request.fetch for custom fetch implementations
• request.fetchOptions for undici dispatchers / per-instance proxies
• no more process-wide setGlobalDispatcher needed
🖼 Better editMessageMedia uploads
• media now accepts Buffer / stream / local path
• thumbnail / cover uploads work…
🚀 node-telegram-bot-api v1.1.0 is out — with full Bot API 10.1 support!
✨ Rich Messages
• sendRichMessage / sendRichMessageDraft
• editMessageText now accepts rich_message (new single-object call)
• new InputRichMessage type, auto-serialized
🤝 Join Request Queries
• answerChatJoinRequestQuery
• sendChatJoinRequestWebApp
📦 npm i [email protected]
📝 Changelog: v1.1.0
Big thanks to danielperez9430 for land…
🚀 node-telegram-bot-api v1.0.0 is out!
Fully rewritten in TypeScript 🎉
🔷 Bundled types - drop @types/node-telegram-bot-api
🧩 Types auto-generated from the official Bot API docs
📦 ESM-only Node.js 18+
🤖 Latest Bot API coverage + new sendLivePhoto
🕊 Dependency free
⚠️ Breaking changes from 0.6x - read the migration guide first 👇
https://github.com/yagop/node-telegram-bot-api/blob/master/CHANGELOG.md#migrating-from-v…
🎉 New release v0.67.0 🎉
Added:
1. Support Telegram Bot API v7.4 (by @danielperez9430)
* #refundStarPayment
2. Support Telegram Bot API 7.6 (@danielperez9430)
* #sendPaidMedia
3. Support Telegram Bot API v7.9 (by @danielperez9430)
4. Support Telegram Bot API v7.10 (by @danielperez9430)
* Update: purchased_paid_media
5. Support Telegram Bot API v8.0 and v8.1
* #savePreparedInlineMessage (@IsmailBinMujeeb)…
New release v0.65.1 🎉
1. Support for updates (@danielperez9430)
message_reaction
message_reaction_count
chat_boost
removed_chat_boost
https://www.npmjs.com/package/node-telegram-bot-api
New release v0.50.0
Added:
Support Bot API v4.8: (by @danielperez9430)
Add methods: sendDice()
Support Bot API v4.7: (by @danielperez9430)
Add methods: getMyCommands(),setMyCommands()
Support Bot API v4.5: (by @danielperez9430)
Add methods: setChatAdministratorCustomTitle()
Support Bot API v4.4: (by @danielperez9430)
Add methods: setChatPermissions()
Support for p…
New Release, v0.30.0 (https://github.com/yagop/node-telegram-bot-api/releases/tag/v0.30.0):
Added:
1. Support Bot API v3.5: (by @GochoMugo)
- Allow provider_data parameter in TelegramBot#sendInvoice
- Add method TelegramBot#sendMediaGroup()
2. Support Bot API v3.4: (by @kamikazechaser)
- Add methods TelegramBot#editMessageLiveLocation, TelegramBot#stopMessageLiveLocation (#439)
…
Signed GochoMugo
Showing the 12 most recent of 20 posts we hold for @node_telegram_bot_api. 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.
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.
Handles this channel named that no longer answer
Dead references
16
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
15
vacant every time we have ever looked
@node_telegram_bot_api named 16 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@ledamint named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 26 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@crazyabdul named in 1 post, 8 August 2026 – 8 August 2026
@dimawebmaker named in 1 post, 8 August 2026 – 8 August 2026
@evolun named in 1 post, 8 August 2026 – 8 August 2026
@githugger named in 1 post, 8 August 2026 – 8 August 2026
@hufan named in 1 post, 8 August 2026 – 8 August 2026
@jiejiss named in 1 post, 8 August 2026 – 8 August 2026
@jlsjonas named in 1 post, 8 August 2026 – 8 August 2026
@libertylocked named in 1 post, 8 August 2026 – 8 August 2026
@melroy89 named in 1 post, 8 August 2026 – 8 August 2026
@ni2c2k named in 1 post, 8 August 2026 – 8 August 2026
@sidelux named in 1 post, 8 August 2026 – 8 August 2026
@sp3ricka named in 1 post, 8 August 2026 – 8 August 2026
@xjx0106 named in 1 post, 8 August 2026 – 8 August 2026
@capacitorset named in 1 post, 8 August 2026 – 8 August 2026
@zhangpanyi named in 1 post, 8 August 2026 – 8 August 2026
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 September 2026 — this
entry's latest reading, not the date you are reading this.
“Node Telegram Bot API” (@node_telegram_bot_api), 2,208 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/node_telegram_bot_api.
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.