Channel
@QRMint
On this record: Growth · Engagement · Posts · Citations · Cite this entry
32subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002209488231 |
|---|---|
| Type | Channel |
| Username | @QRMint |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/QRMint |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 19:18 | 32 | +1 |
| 11 Aug 2026, 03:16 | 31 | no change |
| 7 Aug 2026, 16:28 | 31 | first reading |
20 posts held, back to 26 May 2026 — 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 page of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (26 May 2026 – 7 August 2026) |
| Views total | 8 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 03:16 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
🚧 Maintenance Work at QR Mint 🚧 Dear users, We would like to inform you that QR Mint will undergo scheduled maintenance. This is necessary to enhance the platform’s performance, improve stability, and ensure a seamless user experience. ⏳ Platform Access: During the maintenance period, the platform may be temporarily unavailable. We are working diligently to complete the updates as quickly as possible and provide …
🚀 Hi everyone! We're starting to gather the first participants for the closed beta of the HardCore Arena Level Editor. Over the next few days, we'll grant access to the first creators who want to build their own levels and help shape the future of the game. What will you get? 🎮 Create your own levels Design maps using the Level Editor. Test and publish your creations. 🖼 Turn your levels into NFTs Each level ca…
🚀 Hello everyone! We're excited to announce that QR Mint has a new blockchain partner — BotChain. We've successfully completed the BotChain integration into QR Mint, and over the coming weeks we'll begin connecting our other projects through the QR Mint infrastructure. Why is this important? Our goal is to build multi-chain infrastructure that allows businesses and developers to work across multiple blockchain ec…
🚀 Hello everyone! Earlier, I shared that we're building two new modules for QR Mint. In the previous post, I introduced our Loyalty Program Module. Today I'd like to share the second one: Liquidity Pool Module (DEX Reward Module). We're initially building this module for HardCore Arena, but the concept goes far beyond a single game. It can be applied to gaming tournaments, gaming communities, and many other Web3 …
🚧 Maintenance Work at QR Mint 🚧 Dear users, We would like to inform you that QR Mint will undergo scheduled maintenance. This is necessary to enhance the platform’s performance, improve stability, and ensure a seamless user experience. ⏳ Platform Access: During the maintenance period, the platform may be temporarily unavailable. We are working diligently to complete the updates as quickly as possible and provide …
👋 Hi everyone! It's been a while since our last update, so we'd like to share what we've been working on. Right now, we're developing two major modules for QR Mint. Today, we'd like to introduce one of them: QR Mint Loyalty Program. Our goal is to make it easy for businesses to launch digital loyalty programs powered by NFTs. What's already implemented? ✅ A single NFT can now include multiple partner benefits a…
☕️ We've Launched the SAVE COFFEE Partner Program We're excited to continue growing the SAVE COFFEE movement. Our first international campaign is dedicated to supporting coffee farmers in Ethiopia. As the next step, we're building a global network of partner coffee shops. We've prepared a partnership presentation that explains: • how the partner program works; • the benefits for coffee shops; • how businesses can…
Hello everyone! We have migrated to our new Telegram username: @hardcore_arena_bot. Please use @hardcore_arena_bot to access the project from now on. Thank you for your continued support!
☕️ Hello everyone! We recently launched the SAVE COFFEE NFT Collection on QR Mint, and today we're excited to take the next step by launching the official SAVE COFFEE Community. 👉 https://t.me/+UlaRhMisIX1hMTYy Our mission is to bring together coffee lovers, coffee shops, companies, and partners into one global movement. We have already started connecting with coffee shops, including those that actively manage th…
Hello everyone 👋 We’ve updated the game mechanics. Based on your feedback, we removed attempt limits on free levels — now you can play and fully immerse yourself in the game without restrictions. We realized that early limits were making it harder to get comfortable with the game, so we made onboarding smoother and more open. Tickets are still part of the game — they are now used for participating in free tournam…
🎨 Mint Your QR Art NFT Do you have your own image that you want to transform into QR Art? Create your QR Art NFT and become part of the public QR Art wall on QR Mint. What you get: • Your QR Art will be displayed on the QR Mint website (https://qr-mint.net/en/qr-arts/ton) • The opportunity to become part of the early QR Art community • Access to a new visual and social movement in its early stage • Support in the…
QR Art in QR Mint In QR Mint, we’ve built a simple bot that converts images into QR Art — no NFT and no complex processes. You can try it right now and create your first QR Art: 👉 https://t.me/ArttQR_bot Alongside this, we’ve launched a community dedicated to QR Art / QR Code culture: 👉 https://t.me/+uzjXc1Vg93RhMzRi The goal of the community is to explore and develop QR Art as a form of visual expression, and ov…
Showing the 12 most recent of 20 posts we hold for @QRMint. 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 — 494,846 of 1,629,535 entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“QR Mint News” (@QRMint), 32 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/QRMint.
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.