Telegram RegisterThe public register of Telegram

Channel

Node Telegram Bot API

@node_telegram_bot_api

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

2,230subscribers

-2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001003566237
TypeChannel
Username@node_telegram_bot_api
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/node_telegram_bot_api

Growth

2,2302,2352,232.56 August 2026 — 2,232 subscribers6 August 2026 — 2,233 subscribers9 August 2026 — 2,235 subscribers12 August 2026 — 2,230 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -2. 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,229–2,236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:172,230-5
9 Aug 2026, 23:322,235+2
6 Aug 2026, 23:352,233+1
6 Aug 2026, 16:062,232first 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 pagesof 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
ReactionCountShareShare, drawn
🔥1931.7%
❤1626.7%
👍1321.7%
👏915.0%
👎23.33%
🥰11.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 60reactions 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.

Recent posts

14 Jul 2026, 16:57 UTC≈1,110 views8 reactionsread 7 August 2026

🚀 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…

👍5❤3

Signed Yago

25 Jun 2026, 09:52 UTC≈1,920 viewsread 7 August 2026

🛠 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

Signed Yago

22 Jun 2026, 20:42 UTC≈1,970 views8 reactionsread 7 August 2026

🛠 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…

❤6👍2

Signed Yago

13 Jun 2026, 10:51 UTC≈2,130 views10 reactionsread 7 August 2026

🚀 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…

❤6🔥4

Signed Yago

12 Jun 2026, 23:41 UTC≈1,920 views31 reactionsread 7 August 2026

🚀 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…

🔥14👏9👍6👎2

Signed Yago

13 Dec 2025, 02:28 UTC≈7,020 viewsread 7 August 2026

🎉 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)…

Signed gm

21 May 2024, 12:00 UTC≈16,100 views3 reactionsread 7 August 2026

New release v0.66.0 Support Telegram Bot API 7.2 & 7.3 (@danielperez9430) - getBusinessConnection - replaceStickerInSet Support for updates: (@danielperez9430) - business_connection - business_message - edited_business_message - deleted_business_messages Minor fixes: (@danielperez9430) - getUserChatBoosts

❤1🔥1🥰1

Signed Yago

10 Mar 2024, 04:53 UTC≈16,200 viewsread 7 August 2026

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

Signed Yago

8 Mar 2024, 23:27 UTC≈12,500 viewsread 7 August 2026

New release v0.65.0 🎉 1. Support Telegram Bot API v7.1 deleteMessages (@Sp3ricka) copyMessages (@xjx0106 & @Sp3ricka) setMessageReaction (@Sp3ricka) forwardMessages (@danielperez9430) getUserChatBoosts (@danielperez9430) 2. Minor changes: (@danielperez9430) Refactor methods order Fix copyMessages & setMessageReaction methods Added missing tests Fix tests for methods copyMessages & getMyDefaulAdministratorRights ht…

Signed Yago

22 Dec 2020, 23:16 UTC≈32,900 viewsread 7 August 2026

New release v0.51.0 Added: 1. Support Bot API v5.0: (by @danielperez9430) * Add method *copyMessage()* * Add method *unpinAllChatMessages()* * Add method *close()* * Add method *logOut()* Changed: (by @danielperez9430) * Remove trailing-spaces * Fix Bugs in Test New Test: (by @danielperez9430) * copyMessage * unpinAllChatMessages ✨ Special thanks to @kamikazechaser and @dani…

Signed Yago

13 May 2020, 13:39 UTC≈32,400 viewsread 7 August 2026

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…

Signed Kamikaze Chaser

21 Dec 2017, 12:00 UTC≈31,000 viewsread 7 August 2026

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.

Citation-graph rank

Citation-graph rank — 378,857 of 1,480,688entries 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.

Tecnonucleous
@Tecnonucleous · 7381 post

Names

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

Parked Domain
@kamikazechaser · 345 posts@sidelux
@GingerPlusPlus · 51 post@Lord
@TheBeastOfCaerbannog · 11 post

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

“Node Telegram Bot API” (@node_telegram_bot_api), 2,230 subscribers as measured 12 August 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.