Telegram RegisterThe public register of Telegram
Telegram profile photo for @mtproto/core

Channel

@mtproto/core

@mtproto_core

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

237subscribers

-2 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-1001257342023
TypeChannel
Username@mtproto_core
CreatedBetween 1 March 2018 and 4 May 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/mtproto_core

Growth

2372392387 August 2026 — 239 subscribers8 August 2026 — 239 subscribers24 August 2026 — 237 subscribers7 August 202624 August 2026
3 measurements spanning 17 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 237–239 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 23:42237-2
8 Aug 2026, 09:49239no change
7 Aug 2026, 22:16239first reading

Engagement

20 posts held, back to 4 May 2020the 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 2 July 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

40 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1845.0%
🔥1640.0%
👏37.50%
12.50%
❤‍🔥12.50%
👎12.50%

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 3 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 40reactions 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 4 May 2020 to 2 July 2023, 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

2 Jul 2023, 16:41 UTC≈1,250 views18 reactionsread 8 August 2026

In version 6.3.0, the layer was updated to 158!

🔥15👍3

Signed Ali Gasymov

19 Mar 2022, 07:54 UTC≈2,120 views17 reactionsread 8 August 2026

In version 6.2.0, the layer was updated to 139!

👍12👏3❤‍🔥1👎1

Signed Ali Gasymov

22 Dec 2021, 08:52 UTC≈2,460 views5 reactionsread 8 August 2026

In version 6.1.1, the pako dependency import has been fixed. Thanks, RuslanAsadov! Some dependencies have also been updated.

👍31🔥1

Signed Ali Gasymov

2 Dec 2021, 12:02 UTC≈2,460 viewsread 8 August 2026

In version 6.1.0, the layer was updated to 133 (this fixes the UPDATE_APP_TO_LOGIN error). Thanks, Pogudin Segrey!

Signed Ali Gasymov

4 Apr 2021, 12:35 UTC≈2,670 viewsread 8 August 2026

In version 6.0.1 fixed the import path and added the debug module to the dependencies. Thanks, alexpts!

Signed Ali Gasymov

3 Apr 2021, 08:09 UTC≈2,370 viewsread 8 August 2026
Photo

In version 6.0.0: The documentation is written from scratch and posted on https://mtproto-core.js.org/ website Updated the IP for the second DC (thanks, sg-4xxi) Rethought storage and custom storage Rethought the choice of environment Improved logs in debug mode Removed the types for the typescript

Signed Ali Gasymov

21 Feb 2021, 09:31 UTC≈1,840 viewsread 8 August 2026
Poll

In what environment do you use (or want to use) the library?

  1. Node JS81%
  2. Browser15%
  3. Electron5%
  4. React Native5%
  5. Other5%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Signed Ali Gasymov

31 Jan 2021, 18:30 UTC≈1,550 viewsread 8 August 2026

Screw It, I'll rewrite the @mtproto_core before the summer

Signed Ali Gasymov

28 Nov 2020, 15:43 UTC≈1,690 viewsread 8 August 2026
Photo

In version 5.3.0: Layer has been updated to 121 Most interesting: methods for statistics and comments Updated pako Just keeping the dependencies up-to-date

Signed Ali Gasymov

22 Nov 2020, 14:26 UTC≈1,460 viewsread 8 August 2026
Photo

In version 5.2.0: Problems with reconnecting and hanging fixed To do this, I started storing the socket state in the transport module and add acknowledgment logic for outgoing messages Handle FLOOD_WAIT_X In the guide "Handling common errors" added information about how to handle the FLOOD_WAIT_X error - https://github.com/alik0211/mtproto-core/blob/master/docs/handling-common-errors.md Unit testing and playground

Signed Ali Gasymov

8 Nov 2020, 18:54 UTC≈1,140 viewsread 8 August 2026
Photo

In version 5.1.0: Add counter Now the exact number of bytes is allocated before serialization, thanks to the counter. It fix error RangeError: Source is too large Update authentication guide Added a stage for getting a user. It will help you check whether the user is logged in. I also rewrote the example using a async/await - https://github.com/alik0211/mtproto-core/blob/master/docs/authentication.md

Signed Ali Gasymov

11 Oct 2020, 17:22 UTC≈1,030 viewsread 8 August 2026
Photo

Fix deserialization errors in version 5.0.0. Thank you very much, softforseeker! Also: 1. Add logger (documentation will be available later) 2. Import only inflate from pako 3. Fix the serialization of boolean flags This is a major update, because the logic of serialization and deserialization was rewritten. There are no breaking changes

Signed Ali Gasymov

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

21 Feb 2021, 09:31 UTCAnonymous Poll297 voters

In what environment do you use (or want to use) the library?

  1. Node JS81%
  2. Browser15%
  3. Electron5%
  4. React Native5%
  5. Other5%

The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 4 May 2020 to 2 July 2023. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“@mtproto/core” (@mtproto_core), 237 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/mtproto_core.

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.