Telegram RegisterThe public register of Telegram
Telegram profile photo for Infinity CM2 and [BEST] Official. Pay to Sellers ONLY but not here!

Channel

Infinity CM2 and [BEST] Official. Pay to Sellers ONLY but not here!

@InfinityBox

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

10,560subscribers

-13 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001000046482
TypeChannel
Username@InfinityBox
DescriptionNo direct payments! Pay to Sellers only! https://infinity-box.com
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/InfinityBox

Growth

10,55310,57310,5637 August 2026 — 10,573 subscribers8 August 2026 — 10,569 subscribers9 August 2026 — 10,566 subscribers10 August 2026 — 10,556 subscribers11 August 2026 — 10,559 subscribers12 August 2026 — 10,561 subscribers13 August 2026 — 10,566 subscribers15 August 2026 — 10,565 subscribers16 August 2026 — 10,561 subscribers17 August 2026 — 10,559 subscribers18 August 2026 — 10,561 subscribers19 August 2026 — 10,560 subscribers20 August 2026 — 10,556 subscribers21 August 2026 — 10,553 subscribers23 August 2026 — 10,559 subscribers25 August 2026 — 10,560 subscribers10,5607 August 202625 August 2026
16 measurements spanning 18 days, net -13. 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 10,550–10,576 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:1810,560+1
23 Aug 2026, 10:5810,559+6
21 Aug 2026, 21:0910,553-3
20 Aug 2026, 16:3810,556-4
19 Aug 2026, 19:2310,560-1
18 Aug 2026, 19:4710,561+2
17 Aug 2026, 20:5410,559-2
16 Aug 2026, 17:1810,561-4
15 Aug 2026, 01:0410,565-1
13 Aug 2026, 18:1810,566+5
12 Aug 2026, 13:5710,561+2
11 Aug 2026, 11:5310,559+3
10 Aug 2026, 09:1410,556-10
9 Aug 2026, 08:2110,566-3
8 Aug 2026, 05:4110,569-4
7 Aug 2026, 13:1610,573first reading

Engagement

22 posts held, back to 6 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 29 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
17.2%
avg views ÷ 10,560 subscribers
Avg views / post
1,810
2 posts measured
Reaction rate
0.579%
reactions ÷ views · ER floor
Posts in window
2
of 22 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 August 2026
Posts held22 (6 February 202623 August 2026)
Views total3,626
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 07:50 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.

What this channel posts

Photos
15
Links
551

Lifetime counters from Telegram’s own channel header, read 25 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

325 reactions across 22 posts, in 9 distinct kinds. The most used accounts for 72.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
23772.9%
👍5918.2%
👏92.77%
🔥92.77%
😁51.54%
🆒20.615%
👎20.615%
10.308%
🥰10.308%

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 22 of the 22 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 325reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 6 February 2026 to 23 August 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

23 Aug 2026, 10:39 UTC916 views5 reactionsread 25 August 2026

DumpTool/Kleister v1.12 - Allwinner Car Radio SoC images tested - More file types supported - [PDT] Platform Detector updated to detect more new hardware Download Kleister_PDT_DumpTool_v1.12_NoDongle_pass_1111.7z here https://infinity-box.com/?r=42

5

8 Aug 2026, 10:36 UTC≈2,710 views16 reactionsread 25 August 2026

CM2MT2 v3.17 - Models load method updated, software start much faster - Hisense devices methods updated - bootpack files download method simplified, useless questions removed - Read DUMP function - keys.json creation methods updated, save available keys right on boot, even in case of failure - Backup restore (preloader) issue fixed for number of devices - Useless EMI selection question removed on scatter load - Dest

13🔥2😁1

23 Jul 2026, 14:54 UTC≈3,550 views20 reactionsread 25 August 2026

Infinity CM2SP3 v2.50 - many new models https://infinity-box.com/news/?r=4450 - [AppTool] file list save issue fixed - Fastboot functions updated - EROFS loader updated for latest firmware images - Log files store method returned back to "old good" one file per session - Issue report to Chat removed - RPMB read/write functions updated - Oppo/Realme regionlock reset - Hisense devices methods updated - ZTE/Nubia DA an

13👍5😁2

17 May 2026, 09:49 UTC≈6,330 views28 reactionsread 25 August 2026

#CM2MT2 v3.16 - New models and fixes - Issue with gui and repeated DA/EMI file selection fixed (finally) - Meizu operations updated - "Can''t make a call" method updated - Bootloader unlock method updated - TCL DA updated - [MemTool] option to save pmt to gpt file for latest devices Teclast M40-Plus Hotwav Hyper-7-Pro, Cosmos-U, Cosmos-V5, Cosmos-V9, Cyber-7, Cyber-8, Cyber-9-Pro, Cyber-16-Pro, Cyber-X, Cyber-X-Pro

24👍31

6 May 2026, 11:41 UTC≈6,270 views12 reactionsread 25 August 2026

Free CM2 Online/Digital 24 Hours Go here @keine_frau_bot and type /gift PLEASE READ

10🔥2

6 May 2026, 11:35 UTC≈5,820 views1 reactionsread 25 August 2026

WARNING! Team NEVER ask to pay in Telegram, Whatsapp or other messengers! Talk to well-known sellers only (https://infinity-box.com/buy/) Official contacts (https://infinity-box.com/contact/)

1

30 Apr 2026, 08:10 UTC≈6,770 views18 reactionsread 25 August 2026

CM2MT2 v3.15 - New models and fixes - Scan Filesystems option rebuilded - Issue with gui and repeated EMI file selection fixed - EROFS loader updated for latest firmware images - Mi Account process updated for number of models - [AppTool] updated with more info about loaded files - Minor bugs fixed More models supported: Oukitel WP60 AbcTech X20 AbThree L9 Aermoo M1 Affix T737 Balliance Tab-A3 Barelpoland Cavion-So

10👍4🔥3😁1

26 Apr 2026, 18:54 UTC≈6,050 views23 reactionsread 25 August 2026

[BEST3] v3.00 for all [BEST] Dongle/Activation users

18👍5

19 Apr 2026, 10:39 UTC≈6,890 views15 reactionsread 25 August 2026

If you have Facebook Group with more than 500 members you may write your group link here. Team will join and post Infinity news to your group.

12👏3

19 Apr 2026, 07:29 UTC≈6,950 views24 reactionsread 25 August 2026

Infinity #CM2MT2 v3.14 - v6 DA preloader boot/auth methods updated. Many devices supported and more to come. f.e. KJ7 2026/01, KM6 2026/02, KJ6 2025/09, X6515 2024/10 etc. - EMI/Auth files and model selection method updated for [FF] - Flash file loading method updated - Firmware read process updated for latest devices - Hardware detection issue for number of devices fixed - META mode issue with Device-ID write fix

15👍7👏1😁1

17 Apr 2026, 09:13 UTC≈5,220 views7 reactionsread 25 August 2026

Infinity #CM2RKT v2.03 - Online|Digital mode enabled - Rockchip RK3562 - ADB and Fastboot integration - Many internal changes and improvements

👍51🔥1

4 Apr 2026, 10:18 UTC≈6,240 views6 reactionsread 25 August 2026

Telegram Chat owners can add telegram bot https://forum.infinity-box.com/viewtopic.php?t=30238 We can try to add features on demand. Ask supporters in CM2 chat

6

Showing the 12 most recent of 22 posts we hold for @InfinityBox. 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 — 446,041 of 1,602,822entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

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

“Infinity CM2 and [BEST] Official. Pay to Sellers ONLY but not here!” (@InfinityBox), 10,560 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/InfinityBox.

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.