Telegram RegisterThe public register of Telegram

Channel

Telegraf releases

@Telegraf_JS

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

189subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001700208314
TypeChannel
Username@Telegraf_JS
DescriptionModern bot framework for Node.js https://telegraf.js.org/
CreatedBetween 1 December 2021 and 5 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Telegraf_JS

Growth

1897 Aug 2026, 12:20 — 189 subscribers8 Aug 2026, 12:03 — 189 subscribers7 Aug 2026, 12:208 Aug 2026, 12:03
2 measurements taken within a single day. 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 188–190 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:03189no change
7 Aug 2026, 12:20189first reading

Engagement

20 posts held, back to 5 March 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 7 July 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
27

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

211 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7636.0%
6329.9%
👍4420.9%
🙏125.69%
52.37%
👎31.42%
🥰31.42%
👻20.948%
👏10.474%
💯10.474%
🕊10.474%

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 19 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 211reactions 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 5 March 2023 to 7 July 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

7 Jul 2024, 12:35 UTC≈1,400 views11 reactionsread 8 August 2026

Part 2 of the stream is starting now: https://youtu.be/8lBqkO8PL_A

8👎3

6 Jul 2024, 12:23 UTC≈1,300 views24 reactionsread 8 August 2026

I'm going to be updating Telegraf live on YouTube in 10 minutes! https://www.youtube.com/live/IyslIXMCR74 Edit: to be continued tomorrow 18:00 IST / 12:30 UTC

13👍5🔥4👻2

29 Feb 2024, 07:49 UTC≈1,660 views14 reactionsread 8 August 2026

✨ v4.16.3 Fix: bug with link_preview_options.url caused client to try sending it as media Fix: add CommandContextExtn type to Composer::{start|help|settings} (adds ctx.command, payload, args)

🔥93👍2

26 Feb 2024, 10:04 UTC≈1,160 views3 reactionsread 8 August 2026

✨ v4.16.2 Fixed: ctx.text was undefined when ctx.entities was absent

3

25 Feb 2024, 17:11 UTC945 views5 reactionsread 8 August 2026

✨ v4.16.1 Fixed: ctx.from will use ctx.callbackQuery.from instead of ctx.callbackQuery.message.from

👍31🔥1

25 Feb 2024, 00:24 UTC838 views21 reactionsread 8 August 2026

✨ v4.16.0 🆙 Bot API Updates 7.0 and 7.1 👍 Working with Reactions (bot.reaction, ctx.reactions) 💅 Context::text and Context::entities() helpers 📬 Context::msg and Context::msgId shorthands 🚀 bot.launch takes an onLaunch callback 🖍 quote format helper & stricter types 🔧 Other fixes and improvements There's a major announcement as part of this update. Read the full release notes to find out!

👍8🔥74💯1🥰1

28 Jan 2024, 07:29 UTC783 views5 reactionsread 8 August 2026

New version of @telegraf/session. ⬆️ v2.0.0-beta.7 * Updates minimum version for all peerDependencies (you might need to update your database drivers to match) * Relaxes Kysely version dependency * Telegraf is now a peerDependency, and SessionStore type is reused from Telegraf (Telegraf's Bot API 7.0 update coming soon)

👍3👏1🔥1

3 Dec 2023, 13:20 UTC970 views15 reactionsread 8 August 2026

✨ v4.15.3 Fixed sending local files and streams; uploading thumbnail is now respected.

8👍3🔥3🕊1

30 Nov 2023, 06:17 UTC818 views1 reactionsread 8 August 2026

✨ v4.15.2 EXPERIMENTAL_SESSION_CHECKS introduced in the last minor release had been reporting false positives. This has been fixed; it will now work as intended.

👍1

29 Nov 2023, 20:37 UTC662 views7 reactionsread 8 August 2026

✨ v4.15.1 🔧 Fixed sendPhoto and friends irrecoverably erroring if passed an invalid path, such as a directory. ⚠️ Set the env var EXPERIMENTAL_SESSION_CHECKS=1 to catch session bugs in your code. Enabling this will throw errors if you access/assign to session after middleware chain has exhausted. Read the full release notes.

👍4🔥3

31 Oct 2023, 05:23 UTC≈3,470 views17 reactionsread 8 August 2026

Update: This issue seems resolved by Telegram now; thanks for reporting. Bots should now work normally again. Attention ⚠️: Seems like Telegram Bot API is having trouble, potentially due to an upcoming update, and responds with a "not enough rights" error to many API calls. Be assured this is temporary. Your bots should be back in operation once they fix the issue. Bug report: https://bugs.telegram.org/c/33784

🙏12👍5

23 Oct 2023, 16:55 UTC≈1,150 views12 reactionsread 8 August 2026

✨ v4.15.0 * anyOf and allOf combinators for Composer::on filters. * Deprecating hookPath in bot.launch's webhook options, in favour of path.

👍54🔥3

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

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

“Telegraf releases” (@Telegraf_JS), 189 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Telegraf_JS.

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.