Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇮🇩 Redmi Note 5A Prime / Lite || CHANNEL ||

Channel

🇮🇩 Redmi Note 5A Prime / Lite || CHANNEL ||

@redminote5a_channel

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

2,238subscribers

-17 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001414696237
TypeChannel
Username@redminote5a_channel
CreatedBetween 1 April 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/redminote5a_channel

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 92% 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 1 other registered channel. 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
@redminote5a_channel/1021 · this entry22 Dec 2025, 00:37 UTC@r4xdownloads/281422 Dec 2025, 01:39 UTC1.0062 minutes
@redminote5a_channel/1025 · this entry10 Jan 2026, 12:07 UTC@r4xdownloads/281711 Jan 2026, 09:43 UTC1.0022 hours
@r4xdownloads/282021 Feb 2026, 14:42 UTC@redminote5a_channel/1027 · this entry22 Feb 2026, 13:34 UTC1.0023 hours
@redminote5a_channel/1030 · this entry24 May 2026, 10:28 UTC@r4xdownloads/282226 May 2026, 14:33 UTC1.002 days
@redminote5a_channel/1032 · this entry6 Jun 2026, 16:25 UTC@r4xdownloads/28237 Jun 2026, 05:09 UTC1.0013 hours
@r4xdownloads/281213 Dec 2025, 04:42 UTC@redminote5a_channel/1019 · this entry13 Dec 2025, 15:04 UTC0.9710 hours
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@r4xdownloads6 (6/6 hand-verifiable sample passed)1.0017 hoursthis entry (42)

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 2 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 11 comparable posts for this entry, running 21 October 2025 to 16 July 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 2, the earliest publisher we hold is @r4xdownloads. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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 1 other registered channel, 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

2,2372,2572,2476 August 2026 — 2,255 subscribers7 August 2026 — 2,257 subscribers10 August 2026 — 2,255 subscribers14 August 2026 — 2,252 subscribers17 August 2026 — 2,251 subscribers24 August 2026 — 2,252 subscribers27 August 2026 — 2,253 subscribers30 August 2026 — 2,247 subscribers2 September 2026 — 2,245 subscribers6 September 2026 — 2,240 subscribers11 September 2026 — 2,237 subscribers15 September 2026 — 2,238 subscribers2,2386 August 202615 September 2026
12 measurements spanning 39 days, net -17. 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 2,234–2,260 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 08:392,238+1
11 Sept 2026, 07:152,237-3
6 Sept 2026, 18:592,240-5
2 Sept 2026, 13:032,245-2
30 Aug 2026, 15:352,247-6
27 Aug 2026, 12:162,253+1
24 Aug 2026, 18:452,252+1
17 Aug 2026, 12:282,251-1
14 Aug 2026, 03:132,252-3
10 Aug 2026, 11:482,255-2
7 Aug 2026, 13:172,257+2
6 Aug 2026, 21:312,255first reading

Engagement

20 posts held, back to 21 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of 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 16 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 Jul 2026, 13:18 UTC542 viewsread 7 August 2026
Photo

Mystrile Kernel | Mi8937_4_19 Updated: 16/07/2026 By Cappucino • Initial release • Added Manual Hook xxKSU 🔸Download: Pixeldrain | Telegram 🔸Screenshots: here 🔸xxksu manager Notes: • Target: Xiaomi MSM8937 [Mi8937_4_19] • Redmi 3S / 3X (land) • Redmi 4 Standard (prada) • Redmi 4A (rolex) • Redmi 4X (santoni) • Redmi 5A (riva) • Redmi Note 5A / Y1 Lite (ugglite) • Redmi Note 5A / Y1 Prime (ugg) • There's nothing sp

16 Jun 2026, 04:05 UTC990 viewsread 7 August 2026
Photo

Selamat Tahun Baru Islam 1448 H. Semoga setiap langkah dipenuhi keberkahan, setiap usaha membawa manfaat, dan setiap harapan menemukan jalannya. XFI • TDSPYA • SFX

6 Jun 2026, 16:25 UTC≈1,250 viewsread 7 August 2026
Photo

LineageOS | 23.2 | Baklava QPR2 | Mi8937_4_19 📱Target: Xiaomi MSM8937 [Mi8937_4_19] 👨‍💻Author: @me_cafebabe (Artwork by @Ren_Artworks) 🗓Build Date: June 6, 2026 🛡Security Patch: 2026-06-01 🐧Kernel: 4.19.325-cip133-st17-Mi8937v2-73510-gc93aded75adf 🔍sha256sum: a0299b9 📦Download: [Smash] [Telegram] [OneDrive by Nem1x] (Smash expiry: 14 days) 📋Changelog: - Update to latest LineageOS sources - kernel: Merge LineageOS/

24 May 2026, 10:28 UTC≈1,290 viewsread 7 August 2026
Photo

LineageOS 18.1 for Mi8937 Android version: 11 (R) Kernel version: 4.19.325 Build date: May 24, 2026 Download: [link] Changelog: - May 2026 backported security patches (ASB string fixed to Feb 2024 to avoid safety checks) - Kernel merge: cip132, st16 - Android WebView 148.0.7778.120 - Synced with latest LOS source - Signed with dev-keys Credits: - 0xCAFEBABE - MSe1969 - LineageOS built by zyn

20 Mar 2026, 09:46 UTC≈1,490 viewsread 7 August 2026
Forwarded from @XiaomiFederationIndonesiaPhoto

Mari Saling Memaafkan

22 Feb 2026, 13:34 UTC≈2,610 viewsread 7 August 2026
Photo

Infinity-X | v3.7 | VANILLA | Android 16 (qpr2) | Mi8937_4_19 📱Target: Xiaomi MSM8937 [Mi8937_4_19] 👨‍💻Author: @omansh_krishn 🗓Build Date: Feb 20, 2026 🛡Security Patch: 2026-02-01 🐧Kernel: 4.19.325-cip128-st12-Mi8937v2 📦Download: - ROM [sha256sum: 742e159]: [GITHUB RELEASES] [ONEDRIVE] [SOURCEFORGE] [TELEGRAM] - KSUN [sha256sum: 357cde9]: [GITHUB RELEASES] [ONEDRIVE] [SOURCEFORGE] [TELEGRAM] 🗒Notes: - No n

10 Jan 2026, 12:07 UTC≈2,760 viewsread 7 August 2026
Photo

AxionAOSP v2.3 | Official | Android 16 QPR1 Maintainer: Rve Build date: 09/01/2026 Changelog: source Devices (Mi8937) • Redmi 3S / 3X (land) • Redmi 4 Standard (prada) • Redmi 4A (rolex) • Redmi 4X (santoni) • Redmi 5A (riva) • Redmi Note 5A / Y1 Lite (ugglite) • Redmi Note 5A / Y1 Prime (ugg) ▪️Download ▪️Installation Guide ▪️Support Group Notes • kernel 4.19.x • gapps build using EROFS • use this recovery https

31 Dec 2025, 10:31 UTC≈2,360 viewsread 7 August 2026
Photo

LineageOS | 23.1 | Baklava | Mi8937_4_19 📱Target: Xiaomi MSM8937 [Mi8937_4_19] 👨‍💻Author: @me_cafebabe (Artwork by @Ren_Artworks) 🗓Build Date: December 31, 2025 🛡Security Patch: 2025-12-01 🐧Kernel: 4.19.325-cip126-st10-Mi8937v2-71431-g959fe783a0be 🔍sha256sum: d8ee329 📦Download: [Smash] [Telegram] [OneDrive by Nem1x] (Smash expiry: 14 days) 📋Changelog: - LineageOS 23.1 ❗️Known Issues: - https://t.me/mi_msm8937/812

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

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

“🇮🇩 Redmi Note 5A Prime / Lite || CHANNEL ||” (@redminote5a_channel), 2,238 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/redminote5a_channel.

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.