2 measurements spanning 2 days. 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 118–120 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 04:17
119
no change
7 Aug 2026, 13:01
119
first reading
Engagement
20 posts held, back to 12 July 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 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 January 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
6
Links
17
Lifetime counters from Telegram’s own channel header, read 9 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
175 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 45.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
79
45.1%
custom 5456140674028019486
23
13.1%
👍
17
9.71%
⚡
15
8.57%
❤
12
6.86%
😁
7
4.00%
🤣
7
4.00%
👀
4
2.29%
💯
4
2.29%
🍌
2
1.14%
🤩
2
1.14%
🕊
1
0.571%
😱
1
0.571%
🤯
1
0.571%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 17 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 175reactions 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 July 2024 to 7 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
152
across the posts below
Posts paid on
11
of 18 we hold a reading for · 61%
Most on one post
80
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MiniAppsQuest. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 12 July 2024 to 7 January 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
👨💻 #DevLog № 7: Soar Quest, Archival and Revival
A short story about an old project and its revival.
Soar Quest (v1) was an app development framework I worked on during 2022-2023. The idea at its core was simple: software should take fewer lines of code (to be built). And indeed, I was able to build functional "mini" apps in less than 100 lines of code. Initially, I was building this framework to make cross-platfor…
🤔 #Opinion № 2: The Future of Sales for Mini Apps 🛍
Traditionally, you create a service, setup payments (banks and Stripe), develop an in-house affiliate program or integrate a ready service (both costly options), convince and onboard affiliates, then implement the attribution/distribution of commissions. 😮💨
With the new Telegram Affiliate Programs, it only takes a few clicks. Transactions are already handled by T…
100+ subscribers! 🥳🎉
I would like to use this opportunity to thank you all ☺️ and to ask you a question 👀
❓ Which mini apps do you use at least once a week (besides the Wallet app and games)?
And if you do not use mini apps, what do you think is missing? 🤔
Any thoughts you could share would be very helpful 😉 You can reach me @elbatanony
👨💻 #DevLog № 6: No-code Mini Apps Builder 🖥
Exploring what a no-code Mini Apps builder would look like 🔍 Just a mock-up for now.
Stealing Borrowing design from AppSheet 👨🏻🎨 with a bit of help from v0 ⚡️
🤓 #Tip № 4: Free Storage 💯
For typical apps, a storage bucket is required to store users' files. The most popular solutions are AWS S3 and Google Cloud Storage.
But this is not the case for Telegram Mini Apps. Why? Because Telegram Bots have always stored files by sending them as a message to the user, without needing to store them elsewhere (in most cases). They relied on generous Telegram, as a file storage mediu…
💡 #Idea № 3: The First Fully AI-Automated Apps
I predict that the first fully AI-automated, widely-accessible, non-trivial software application would be something like a Telegram bot. But this statement requires some definitions.
Fully AI-automated: the person creating the app does not interact with any code nor requires any technical knowledge. For example, creating and deploying the Telegram bot solely by chattin…
👨💻 #DevLog № 5: Waitlist Feature ⌛
A minimalist approach demo for a waitlist feature. The user can join and leave a waitlist.
Technical details 👨💻: with the current template setup, the feature took less than a 100 lines of code, in a single file. With one database record per user, that triggers a cloud function that send the message. ⚡️
Here is to celebrate 5️⃣0️⃣ subscribers! 🥳
Other things I'm celebrating 🎉
- Completing my first Mini Apps client project 👨💻
- Telegram still growing 📈 and releasing awesome features ⚡️
- Durov still alive and free (for now) ✈️
Thank you for all your support! ☺️
Hint: your friends can join before tomorrow evening 😉
💡 #Idea № 2: Mini App Subscriptions via Channel Payment Links
Telegram introduced Star Subscriptions to join channels ⭐️ This can be used to power subscriptions for Mini Apps (and bots), and not just channels. Making this one of the simplest subscription implementations around 💪
How does it work?
1. 🔗 Generate a subscription channel invite (payment) link
2. ▶️ Add a button in the Mini App for the user to pay
3. 🤑 U…
🔥5❤3👍1
Showing the 12 most recent of 20 posts we hold for @MiniAppsQuest. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“Mini Apps Quest” (@MiniAppsQuest), 119 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/MiniAppsQuest.
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.