Telegram RegisterThe public register of Telegram

Channel

Poco F4 GT | Updates

@PocoF4GTGlobalUpdates

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

967subscribers

+1 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-1001651592578
TypeChannel
Username@PocoF4GTGlobalUpdates
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/PocoF4GTGlobalUpdates

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 5 other registered channels. They sit inside a group of 7 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@xiaomi13proupdate/28317 Apr 2024, 02:31 UTC@PocoF4GTGlobalUpdates/81 · this entry17 Apr 2024, 02:31 UTC1.00under a minute
@PocoF4GTGlobalUpdates/83 · this entry24 May 2024, 23:21 UTC@xiaomi13proupdate/29124 May 2024, 23:21 UTC1.00under a minute
@xiaomi13proupdate/2921 Jun 2024, 01:30 UTC@PocoF4GTGlobalUpdates/84 · this entry1 Jun 2024, 01:30 UTC1.00under a minute
@xiaomi13proupdate/2932 Jun 2024, 12:33 UTC@PocoF4GTGlobalUpdates/85 · this entry2 Jun 2024, 12:33 UTC1.00under a minute
@xiaomi13proupdate/29626 Jul 2024, 14:00 UTC@PocoF4GTGlobalUpdates/88 · this entry26 Jul 2024, 14:00 UTC1.00under a minute
@xiaomi13proupdate/2982 Sept 2024, 10:32 UTC@PocoF4GTGlobalUpdates/90 · this entry2 Sept 2024, 10:32 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@xiaomi13proupdate6 (6/6 hand-verifiable sample passed)1.00under a minute@xiaomi13proupdate (51)
@RedmiNote11ProPlus5GUpdates6 (6/6 hand-verifiable sample passed)1.00under a minute@RedmiNote11ProPlus5GUpdates (51)
@PocoM6ProUpdates5 (5/5 hand-verifiable sample passed)1.00under a minute@PocoM6ProUpdates (41)
@PocoX6Updates5 (5/5 hand-verifiable sample passed)1.00under a minute@PocoX6Updates (41)
@WhyRedCloud5 (5/5 hand-verifiable sample passed)1.00under a minute@WhyRedCloud (32)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 21 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 17 April 2024 to 2 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 7, the earliest publisher we hold is @WhyRedCloud. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 6 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

966967966.57 Aug 2026, 05:46 — 966 subscribers7 Aug 2026, 08:33 — 967 subscribers7 Aug 2026, 05:467 Aug 2026, 08:33
2 measurements taken within a single day, net +1. 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 966–967 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 08:33967+1
7 Aug 2026, 05:46966first reading

Engagement

20 posts held, back to 17 April 2024the 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.

ERR · 30 days
31.3%
avg views ÷ 967 subscribers
Avg views / post
303
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 20 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 2 August 2026
Posts held20 (17 April 20242 August 2026)
Views total606
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 05: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.

Reaction mix

117 reactions across 16 posts, in 12 distinct kinds. The most used accounts for 29.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3429.1%
👎2420.5%
👍1916.2%
💩1613.7%
🔥75.98%
🖕54.27%
🥰43.42%
🗿32.56%
🤔21.71%
👏10.855%
😁10.855%
🤡10.855%

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 18 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 117reactions 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 17 April 2024 to 2 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

2 Aug 2026, 14:08 UTC225 viewsread 7 August 2026
Photo

OrangeFox Recovery R12.0_1| UNOFFICIAL | Android A14-A16 | POCOF4GT | HOTFIX Update: 02/08/2026 #Ofox #OrangeFox #Twrp #Recovery #A14 #A16 #Ingres • Download : Img | Zip • Screenshots: Photos Notes: • Supports Hybrid OS A14-A16 • Fixed Vibration makes the recovery slow • Pre-release, expect bugs • It should work on AOSP; please report any bugs. • If you found bug, you can tell me with logs Thanks support for All

Signed MeHighG

29 Jul 2026, 13:12 UTC381 viewsread 7 August 2026
Photo

VoltageOS 5.11-EOL - UNOFFICIAL #VoltageOS #ROM #A16 Android version: 16. Build date: 26/07/'26 EOL means end of A16. Next release will be on A17. • Download Vanilla • Download ReSukiSU patched boot > Notes • Use latest firmware. • To flash this ROM, use latest TWRP or OFRP. • Do not try to install 'full' variant of NikGApps, you will get boot-loop until ROM re-flash. > Credits • @itzParsaYC — developing device-t

Signed MeHighG

10 Jul 2026, 06:52 UTC864 views3 reactionsread 7 August 2026
Photo

#RisingOS #ROM #Alpha RisingOS 9.0-Alpha - OFFICIAL | Android 16 QPR2 Updated: 07/10/'26 • Download Changelogs: • Drop 32bit support. • Switch to armv9-a. • Drop useless powershare hal. Notes: • Use latest firmware • Use this twrp Credits: • Big thanks to @n08ik0 for several helps, in testing and developments. • Big thanks to @Darakkyar for providing server. • Thanks @mrmatiaas for testing. • @ArianK16a for base xi

2🔥1

Signed MeHighG

29 Jun 2026, 10:15 UTC887 views5 reactionsread 7 August 2026
Photo

VoltageOS 5.10 - UNOFFICIAL #VoltageOS #ROM #A16 #QPR2 #unofficial Android version: 16. Build date: 29/06/'26 • Download Vanilla • Download SukiSU included • Download SukiSU Ultra APK > Changes • Bluetooth MAC is fixed. • Tweaked some Dalvik VM props. > Notes • Use latest firmware. • To flash this ROM, use latest TWRP or OFRP. • Do not try to install 'full' variant of NikGApps, you will get boot-loop until ROM re-

3👍2

Signed MeHighG

14 Jun 2026, 22:40 UTC≈1,130 views3 reactionsread 7 August 2026
Photo

RealmeUI 7 for ingres Android version: 16 Port Date: 11/06/2026 Download: MEGA DRIVE KSU APP ⚠️Dirty Flash may have bugs or not boot, test by urself Enable Game Turbo New - Features Fastboot Flash bootlop fixed Fixed Dynamic Island position Fixed Small Control Center Custom Resolutions added! Old - Features Issues •DT2W not working •AOD not working Honorable Mentiones •Ty @Mahdi_48111 and @Gurinbone01 f

👍21

Signed MeHighG

12 Jun 2026, 16:37 UTC≈1,020 views8 reactionsread 7 August 2026
Photo

Poco F4 GT/ Redmi K50G - Ingres Project Infinity X 3.11 - UNOFFICIAL - A16 #ProjectInfinityX #ROM #A16 Android version: 16 QPR2 Build date: 12/06/26 GAPPS BUILD |- Download -| |- Mirror -| > Change-log • Initial Release of Project Infinity X 3.11 A16 QPR2 • July Security Patch • Rom Changelog here • Added Dolby Atmos • Added Miui Camera • KernelSU Next updated to 3.2.0 • AOD delay to unlock fixed > Notes • Tri

🔥42👍2

Signed MeHighG

31 May 2026, 15:20 UTC≈1,190 views6 reactionsread 7 August 2026
Photo

RealmeUI 7 for ingres Android version: 16 Port Date: 26/05/2026 Download: MEGA DRIVE ⚠️!IF U FLASH VIA TWRP/OFOX, FORMAT DATA, IF U CANT FORMAT DATA GO TO FASTBOOT AND TYPE: fastboot -w !⚠️ Known issues •Face Unlock Not Working •AOD not working Features • Optimized for daily usage • Bluetooth, NFC working • Debloated • Netflix and other apps fixed HM •Ty @Mahdi_48111 for all the help and fixes •Ty Luna and

6

Signed MeHighG

8 Mar 2026, 07:01 UTC≈2,540 views18 reactionsread 7 August 2026
Photo

#ProjectInfinityX #UNOFFICIAL #ROM #A16 #ingres Project Infinity X 3.8 - UNOFFICIAL | Android 16 (QPR2) Released: 06/03/'26 ▪️Download ▪️Support Changelog: • Initial release of Project Infinity X 3.8 A16 QPR2 • March Security Patch Notes: • GAPPS build • KernelSU Next included • Use latest TWRP or OrangeFox recovery to flash • If the device does not boot, flash the ROM again and reboot Credits: • @itzParsaYC for

13👍2🔥2🥰1

Signed <Hyperterminal_Reborn/>

1 Mar 2026, 19:26 UTC≈2,200 views3 reactionsread 7 August 2026
Photo

Presenting the Poco F8 Pro and Poco F8 Ultra series Poco F8 Pro Join @PocoF8ProGlobal Follow @pocof8proglobalupdates Poco F8 Ultra Join @pocof8ultra_global Follow @PocoF8UltraUpdates

🗿3

Signed <Hyperterminal_Reborn/>

3 Mar 2025, 09:30 UTC≈5,370 views1 reactionsread 7 August 2026

any issues about groups/Channels contact me I am online now

🤡1

Signed ραикαנ || ιя㊉инят #gαиg

2 Sept 2024, 10:32 UTC≈8,100 views14 reactionsread 7 August 2026

https://t.me/PocoF4Discussions Poco F4 (Munch) new discussion group.. Old one is off for some reason.. Join if you're interested. Thank you..🙏 --- Admin team

👍63👎2🤔2😁1

Signed ραикαנ || ιя㊉инят #gαиg

30 Aug 2024, 13:55 UTC≈7,750 views3 reactionsread 7 August 2026

https://discord.com/invite/XjRH85uD Our discord server joined every one here too

👎21

Signed ραикαנ || ιя㊉инят #gαиg

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

Mentions

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

“Poco F4 GT | Updates” (@PocoF4GTGlobalUpdates), 967 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/PocoF4GTGlobalUpdates.

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.