Telegram RegisterThe public register of Telegram
Telegram profile photo for Infinity X Announcements

Channel

Infinity X Announcements

@ProjectInfinityX

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Referenced elsewhere · Cite this entry

27,647subscribers

+1,326 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001817395083
TypeChannel
Username@ProjectInfinityX
DescriptionOfficial Announcements / Information for the Project Infinity X. Discussion: @InfinityXGroup Device Updates: @InfinityXUpdate Website: https://projectinfinity-x.com
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/ProjectInfinityX

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 68% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

26,32127,64726,9846 August 2026 — 26,321 subscribers6 August 2026 — 26,333 subscribers7 August 2026 — 26,364 subscribers8 August 2026 — 26,393 subscribers9 August 2026 — 26,432 subscribers10 August 2026 — 26,475 subscribers11 August 2026 — 26,538 subscribers12 August 2026 — 26,579 subscribers13 August 2026 — 26,604 subscribers15 August 2026 — 26,642 subscribers16 August 2026 — 26,720 subscribers17 August 2026 — 26,773 subscribers18 August 2026 — 26,810 subscribers19 August 2026 — 26,820 subscribers20 August 2026 — 26,847 subscribers21 August 2026 — 26,889 subscribers23 August 2026 — 26,922 subscribers24 August 2026 — 26,980 subscribers25 August 2026 — 27,006 subscribers26 August 2026 — 27,040 subscribers27 August 2026 — 27,062 subscribers28 August 2026 — 27,090 subscribers29 August 2026 — 27,117 subscribers31 August 2026 — 27,152 subscribers1 September 2026 — 27,173 subscribers1 September 2026 — 27,193 subscribers3 September 2026 — 27,228 subscribers4 September 2026 — 27,303 subscribers7 September 2026 — 27,395 subscribers10 September 2026 — 27,427 subscribers12 September 2026 — 27,491 subscribers14 September 2026 — 27,550 subscribers16 September 2026 — 27,594 subscribers18 September 2026 — 27,647 subscribers6 August 202618 September 2026
34 measurements spanning 43 days, net +1,326. 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 26,122–27,846 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 08:3827,647+53
16 Sept 2026, 00:1827,594+44
14 Sept 2026, 08:5727,550+59
12 Sept 2026, 17:3827,491+64
10 Sept 2026, 16:4127,427+32
7 Sept 2026, 17:1827,395+92
4 Sept 2026, 20:1627,303+75
3 Sept 2026, 06:3627,228+35
1 Sept 2026, 21:5427,193+20
1 Sept 2026, 01:1727,173+21
31 Aug 2026, 00:4327,152+35
29 Aug 2026, 22:3327,117+27
28 Aug 2026, 19:1727,090+28
27 Aug 2026, 20:2527,062+22
26 Aug 2026, 22:1227,040+34
25 Aug 2026, 19:1527,006+26
24 Aug 2026, 22:3526,980+58
23 Aug 2026, 10:2526,922+33
21 Aug 2026, 22:3726,889+42
20 Aug 2026, 14:5226,847first reading

Engagement

30 posts held, back to 4 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 66 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
38.8%
avg views ÷ 27,647 subscribers
Avg views / post
10,700
10 posts measured
Reaction rate
3.48%
reactions ÷ views · ER floor
Posts in window
11
of 30 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 25 September 2026
Posts held30 (4 May 2026 – 25 September 2026)
Views total107,380
Reactions total3,732
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 19:46 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
≈1,700
Videos
≈19
Links
≈853

Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
4m 45s
Average length
1m 11s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

9,587 reactions across 29 posts, in 16 distinct kinds. The most used accounts for 51.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4,95951.7%
🔥3,09132.2%
👍2943.07%
❤‍🔥2362.46%
🗿1681.75%
😍1451.51%
🤣1061.11%
🥰1001.04%
🤔971.01%
😁860.897%
👏770.803%
🆒600.626%
🌚560.584%
😎480.501%
🤗450.469%
💯190.198%

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

Measured over the 30 most recent posts we hold, published 4 May 2026 to 25 September 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

25 Sept 2026, 12:06 UTC≈5,210 views263 reactionsread 26 September 2026
Forwarded from @techkarancloudPhoto

🚀 Finally here! Project Infinity X v4.0 ft. Android 17 👉 All Android 16 Features are back 🤯 👉 New Features? 😁 👉 Most Customizable Android 17 Custom ROM yet? 👀 Must watch 💫 https://youtu.be/a1w3Jj61mHg 💫 https://youtu.be/a1w3Jj61mHg Also don't miss out: ⚡️ Best Tweaks/Mods for Rooted Phone ft. 2026 Edition ⚡️ Android 17 Best Features ⚡️ LineageOS Secure edition? ft. MicroG Edition

😍125❤67🔥39👍10🗿6👏4😎4🌚3

Signed Tejas

24 Sept 2026, 02:09 UTCviews —

Infinity X Announcements pinned «The Android 17 (v4.0) source is pushed to https://github.com/ProjectInfinity-X/manifest and is ready to build! ❤️ Screenshots However our last v3.12 (Android 16 source) will be always available at https://github.com/ProjectInfinity-X/manifest/tree/16 and…»

24 Sept 2026, 02:09 UTC≈7,540 views215 reactionsread 26 September 2026

Our current discussion group, "@InfinityXGroup", is undoubtedly a great place to discuss the rom and report issues/bugs. However, I feel that a lot of irrelevant messages also take place there, which sometimes overshadows actual bug reports and causes real user-reported issues to get missed. To address this, we will now be using our Github Issue Tracker. 🔗 Open your issue report here: https://github.com/ProjectInfi…

❤176👍16🥰8🗿4👏3🔥3🆒2❤‍🔥1

Signed Tejas

24 Sept 2026, 01:15 UTC≈10,500 views254 reactionsread 26 September 2026

The Android 17 (v4.0) source is pushed to https://github.com/ProjectInfinity-X/manifest and is ready to build! ❤️ Screenshots However our last v3.12 (Android 16 source) will be always available at https://github.com/ProjectInfinity-X/manifest/tree/16 and is EOL from my side now. (last known changes) Consider applying for OFFICIAL maintainership if you'd like to officially bring it to your device: https://projectin…

❤180🔥54❤‍🔥8🗿6👍3👏2💯1

Signed Tejas

23 Sept 2026, 03:13 UTC≈11,300 views1,122 reactionsread 26 September 2026

Project Infinity X v4.0 (Android 17) - Just a few hours away from reaching your devices! 😃 Basically every feature from our v3.x releases has been brought back, except for lockscreen clock customizations and some of the more extensive Ambient Display and Launcher features. I'll do my best to bring those back too by October. For now, the initial source release will be marked as Beta so that I can gather valuable f…

❤888❤‍🔥100🔥53👍22🤗20🥰17👏9🗿7

Signed Tejas

23 Sept 2026, 03:13 UTC≈8,210 views104 reactionsread 26 September 2026
Photo

Photo, posted without a caption

🔥80❤13❤‍🔥5🗿3🥰3

Signed Tejas

23 Sept 2026, 03:13 UTC≈7,290 views50 reactionsread 26 September 2026
Photo

Photo, posted without a caption

❤37🔥7❤‍🔥3🗿3

Signed Tejas

23 Sept 2026, 03:13 UTC≈3,930 views48 reactionsread 23 September 2026
Photo

Photo, posted without a caption

🔥36❤9🗿3

Signed Tejas

13 Sept 2026, 16:14 UTC≈14,000 views783 reactionsread 23 September 2026
Photo

please don’t mind, sweeties 🥺 I’ve got caught up by some very urgent personal work to do, so I’ll need just a little more time, just a few more days, I promise 🥺 👉👈

❤506🤣106❤‍🔥38👍35🗿29🔥17🤔17🤗16

Signed Tejas

9 Sept 2026, 20:56 UTC≈20,800 views573 reactionsread 23 September 2026

This Sunday!

🔥454❤‍🔥31🤔26😎19❤17🆒8🗿7👏4

Signed Tejas

9 Sept 2026, 20:56 UTC≈18,600 views320 reactionsread 23 September 2026
Video

Video, posted without a caption

🔥251❤23😁13🗿11😎11🆒4❤‍🔥2👏2

Signed Tejas

10 Aug 2026, 05:17 UTC≈49,300 views597 reactionsread 23 September 2026

Greetings, everyone! While work on @ProjectInfinityX v4.0 (Android 17) is underway, here are some additional changes made for our version 3.12 (Android 16). Changelog for @ProjectInfinityX v3.12 releasing since 10/08/2026: - Complete Android 16 ROM Screenshots NOTE: As always the author’s name is listed at the end of line for each change (wherever applicable) to give proper credit for their respective work used in…

❤456🔥85👍18🥰12👏7🗿7😍6❤‍🔥5

Signed Tejas

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

Posts edited after publishing

@ProjectInfinityX edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 August 2026
Most recent edit
10 August 2026

Forward network

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.

Mentions

Named by 180 registered channels — 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

ProjectMatrixx
@projectmatrixx · 5,044
#1
risingOS - News
@RisingOS_news · 8,858
#2
ProjectBlaze | Updates
@projectblazeupdates · 2,577
#3
DroidX-UI // Official Updates
@DroidXUI_announcements · 1,823
#4
AlphaDroid-releases
@alphadroid_releases · 4,070
#5
EverestOS [Paused]
@EverestOS · 900
#6
pawelik channel
@pawelikchannel · 591
#7
Project Sakura | News
@ProjectSakuraNews · 516
#8
Poco F5 / Redmi Note 12 Turbo | Updates
@Poco_F5Official · 11,639
#9
CherishOS
@CherishOS · 6,565
#10
Clarence's Repository
@clarencerepo · 1,641
#11
GenesisOS | Updates
@TheGenesisOS · 914
#12
Redmi Note 8/8T | UPDATES
@GinkgoUpdates · 7,079
#13
Poco X3 Pro | Updates
@PocoX3ProUpdates · 20,443
#14
Poco F3/Mi 11X/K40 Updates™
@pocoF3GlobalUpdates · 16,767
#15
Xtended Releases
@xtendedrom · 1,419
#16
Poco F5 Update 🇮🇩
@PocoF5IDUpdates · 7,019
#17
ROGER BUILDS
@rogerbuilds · 350
#18
euclidOS | Updates
@euclidOSupdates · 368
#19
Android dumps
@android_dumps · 5,681
#20
Ashish Technical Services || UPDATES
@Ashishts007 · 7,286
#21
crDroid Updates
@crDroidUpdates · 18,156
#22
PixelOS Releases
@PixelOSOfficial · 11,286
#23
DrDisagree's Projects
@DrDsProjects · 9,325
#24
LineageOS Updates Tracker
@lineageos_updates · 4,661
#25
Pixel Props
@PixelProps · 14,197
#26
BlissROM Updates
@BlissROM_Updates · 4,929
#27
AOSP Tracker
@aosptracker · 4,544
#28
APW | Android Port World
@AndroidPortWorld · 19,808
#29
VoltageOS Announcements
@voltageosannouncements · 3,100
#30
GApps Leaks
@GappsLeaks · 21,446
#31
Mystic GSI Updates
@mysticgsi · 17,124
#32
Mishaal's Android News Feed
@MishaalAndroidNews · 11,787
#33
ATT • Tech News
@agamtechtricks · 6,210
#34
Sweet~Paradise
@sweet_paradisee · 1,019
#35
Loop Projects | #TeamFiles
@loopprojects · 9,725
#36
Superior OS Channel
@superior_os · 3,902
#37
StatiX | Releases & Announcements
@StatiXOSReleases · 1,350
#38
Magisk Base || Magisk modules and other
@magiskmodules22 · 12,837
#39
Google Pixel Hub
@PixelHubUpdates · 12,623
#40
Tech & Leaks Zone
@techleakszone · 19,836
#41
Hyper Reborn Project | by#M•R•T🇲🇨
@black_pink_reborn · 2,341
#42
Play integrity fix NEXT
@PifNEXT · 6,713
#43
TREBLE UNIVERSE 🇧🇷
@TrebleUniverse · 3,279
#44
Home Screen Setup/Walls Android
@androidhomesetup · 4,037
#45
N0kernel Releases
@N0kernels · 2,922
#46
Poco F5 (marble) Updates
@marble_updates · 506
#47
halcyon: announcements
@hlcynprjct · 1,009
#48
Depth Wallpapers
@Depth_Wallpapers_official · 7,198
#49
APC - Android Ports Cloud
@apcports2 · 8,793
#50
Wallpaper Walli
@Wallpaper_Walli · 7,208
#51
DroidX-UI Screenshots Gallery
@droidxui_screenshots · 461
#52
Amoled Walls | Cloud
@DarkAmoledWalls · 11,499
#53
Google News | En
@google_nws · 26,648
#54
MrSluffy's Prjkt
@mrsluffy_releases · 6,046
#55

Read from Telegram’s recommendation API, most recently 11 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Redmi Note 10 Pro | Updates
@RedmiNote10ProChannel · 22,868
Telegram ranks this channel #17 of 57 here — alongside 56 others — read 19 September 2026
Ayra's Project Channel
@AyraProject · 29,862
Telegram ranks this channel #21 of 41 here — alongside 40 others — read 8 September 2026
APatch Updates
@APatchChannel · 25,201
Telegram ranks this channel #24 of 37 here — alongside 36 others — read 14 September 2026
KernelSU
@KernelSU · 61,920
Telegram ranks this channel #36 of 49 here — alongside 48 others — read 14 September 2026
XM Firmware Updater
@XiaomiFirmwareUpdater · 27,626
Telegram ranks this channel #42 of 56 here — alongside 55 others — read 10 September 2026
SGCam | Official Channel
@googlecameramodbyshamim · 46,258
Telegram ranks this channel #44 of 50 here — alongside 49 others — read 7 September 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Project Infinity X (ru.wikipedia.org)
“…сопровождающих устройств был сохранён.{{Cite web |url=https://t.me/s/ProjectInfinityX/214 |title=Infinity X Announcements |website=Telegram…”
read 20 September 2026

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

“Infinity X Announcements” (@ProjectInfinityX), 27,647 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ProjectInfinityX.

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.