Telegram RegisterThe public register of Telegram

Channel

Redmi S2 Indonesia Channel

@RedmiS2IndonesiaChannel

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

1,055subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001269076655
TypeChannel
Username@RedmiS2IndonesiaChannel
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/RedmiS2IndonesiaChannel

Growth

1,0541,0561,0557 August 2026 — 1,054 subscribers7 August 2026 — 1,054 subscribers10 August 2026 — 1,056 subscribers12 August 2026 — 1,055 subscribers7 August 202612 August 2026
4 measurements spanning 6 days, 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 1,054–1,056 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:031,055-1
10 Aug 2026, 02:111,056+2
7 Aug 2026, 05:301,054no change
7 Aug 2026, 01:461,054first reading

Engagement

20 posts held, back to 5 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
18.0%
avg views ÷ 1,055 subscribers
Avg views / post
190
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 27 July 2026
Posts held20 (5 October 202527 July 2026)
Views total379
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01: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.

Recent posts

27 Jul 2026, 17:18 UTC132 viewsread 7 August 2026
Forwarded from @vinceupdatePhoto

Naughty | 4.19.325 | 4.9.377 | Kernel | Mi8953 Target: Redmi S2/Y2/5/5Plus/Note 4/4X/Mi A1/5X Author: 『 リュウᯓ 』 Build Date: 22/07/26 Kernel: 4.19.325 & 4.9.377 Download : Naughty 4.19 Naughty 4.9 Notes: - Do not use more than one manager because it will cause multiple roots to be detected ins the module. Select one, if you want to change it, delete the installed one and then install another one. - For K4.19 DT2W an

16 Jul 2026, 10:35 UTC247 viewsread 7 August 2026
Forwarded from @Mi_8953Photo

Naughty | 4.19.325 | Kernel | Mi8953 Target: Redmi S2/Y2/5/5Plus/Note 4/4X/MI 5X Author: 『 リュウᯓ 』 Build Date: 16/07/26" Kernel: 4.19.325-chip17-st17 Download: Github Known Issue: https://t.me/Mi_8953/92 Changelog: - fix fingerprint for all variant - fix msm_vidc for sdm450 - Add Mi 5x support - Add support 8 KSU Manager Notes: - Do not use more than one manager because it will cause multiple roots to be detected

9 Jul 2026, 05:31 UTC464 viewsread 7 August 2026
Photo

Kaite - Kernel | Mi8953_a Target: Redmi S2/Y2/5/5Plus/Note 4/4X Build Date: Jul 8, 2026 Kernel: 4.9.377 & 4.19.325 Download: telegram xxksu manager : github Changelog : • Initial Unified for K4.19 • fix Vince & YSL FP "goodix ? Idk" • Bringup Rosy Camera & FP • Initial bringup Rosy for K4.19 (WIP) Credits: • thanks for all contributors By: AmeMika Follow @RedmiS2IndonesiaChannel join @RedmiS2Indonesia #kernel #

30 Jun 2026, 11:27 UTC386 viewsread 7 August 2026
Photo

Mi MSM8953 - Kernel | Mi8953_a Target: Redmi S2/Y2/5/5Plus/Note 4/4X (excluding tissot/daisy/tiffany/sakura) Kernel: 4.9.337 Download: Telegram Initial changelog : https://t.me/me_alts/87 Notes: • Support A11-15 • Fingerprint/Camera/frontflash is not working on Rosy (wip) • "Tissot/Daisy/Tiffany/Sakura" will never be added here because they share the same board, and some also feature A/B versions. Credits: • for

29 Jun 2026, 12:16 UTC353 viewsread 7 August 2026
Forwarded from @vinceupdatePhoto

#LunarisAOSP #baklava #DV #Vanilla LunarisAOSP | 3.11 | Baklava QPR2 | MiThoriumSSI Author: 『 リュウᯓ 』 Build Date : Juni 29, 2026 Target: Mi-Thorium Shared System Image (Mi-Thorium Device) Download Screenshot Install Steps About MiThoriumSSI Changelog: • Sync with latest source Credits : • @me_cafebabe MiThorium stuff • @AmiaAlt Device source • @sammyadityanto For Donat • me for testing :D • All mi8937 & msm8953 dev

27 Jun 2026, 07:09 UTC350 viewsread 7 August 2026
Forwarded from @yoruprojectPhoto

#Voltage #baklava #Yoru Voltage OS | 16.2 | Baklava QPR2 | MiThoriumSSI Author: @rahmatsobrian Build Date : Juni 27, 2026 Target: Mi-Thorium Shared System Image (Mi-Thorium Device) Download: Here (PD Direct) Here (PD+Support Me) Screenshot: Here Install Steps: https://github.com/Mika-Releases/LineageOS_MiThoriumSSI/blob/main/assets/instal.md My Personal Install Steps: https://t.me/yoruprjktdiscuss/297 About MiTh

26 Jun 2026, 08:52 UTC487 viewsread 7 August 2026
Photo

Kaite - Kernel | Mi8953_a Target: Redmi S2/Y2/5Plus/Note 4/4X Build Date: Jun 26, 2026 Kernel: 4.9.377 Download: here Screenshot : v1 & v2 Changelog : - Initial Unified build - more Notes: • SukiSU Manager • Support A11+ • This is an early version for the unified device please report any issues found, especially regarding hardware functions. • Do not use this kernel with the k4.9 ROM created by @AmiaAlt, as it us

26 May 2026, 23:13 UTC759 viewsread 7 August 2026
Photo

✨Selamat Hari Raya Idhul Adha 1447H✨ Mohon Maaf Lahir & Batin "All Admin Redmi S2 Indonesia"

26 May 2026, 12:18 UTC534 viewsread 7 August 2026
Forwarded from @vinceupdatePhoto

#Sakura #baklava #DV Project Sakura | 16.2 | Baklava QPR2 | MiThoriumSSI Author: @Mio5TL Build Date : May 23, 2026 Target: Mi-Thorium Shared System Image (Mi-Thorium Device) Download: Here Install Steps: please read this Screenshot: Here About MiThoriumSSI: https://t.me/mi_msm8937/490 Changelog: • Initial Build MiThoriumSSI A16 QPR2 Credits : • @me_cafebabe MiThorium stuff • @AmiaAlt Device source & help • @samm

25 May 2026, 10:31 UTC729 viewsread 7 August 2026
Photo

ReLIFE | Kernel 4.19 Build Date: 25 Mei 2026 Author @rahmatsobrian Changelog: - Added Krobes hook KernelSU-Next 3.2.0 Notes: Support A13,A15-16 rom with K4.19 maybe or rom with base K4.19 Screenshot: here Download: - Mediafire (ads link, for support me) - PixelDrain (direct link) Don't forget to support the original author who bringup Kernel 4.19 on ysl - Support Group 1 - Support Group 2 Thanks to: - @AmeMikan

23 May 2026, 14:21 UTC430 viewsread 7 August 2026
Forwarded from @vinceupdatePhoto

#EvolutionX #ROM #B #MiThoriumSSI #Unofficial #A16 #Baklava #QPR2 EvolutionX 11.7 | UNOFFICIAL | Android 16 QPR2 | MiThoriumSSI Build Date : May 23, 2026 Target: Mi-Thorium Shared System Image (Mi-Thorium Device) Download: Here Install Steps: please read this Screenshot Here Support Group About MiThoriumSSI: https://t.me/mi_msm8937/490 Changelog: • Initial Build MiThoriumSSI A16 QPR2 Credits : • @me_cafebabe MiT

Signed RenzAlt

23 May 2026, 02:12 UTC420 viewsread 7 August 2026
Forwarded from @vinceupdatePhoto

#infinityX #baklava #DV Project InfinityX | 3.10 | Baklava QPR2 | MiThoriumSSI Author: @Mio5TL Build Date : May 22, 2026 Target: Mi-Thorium Shared System Image (Mi-Thorium Device) Download: Here Install Steps: please read this About MiThoriumSSI: https://t.me/mi_msm8937/490 Changelog: • Initial Build MiThoriumSSI A16 QPR2 Credits : • @me_cafebabe MiThorium stuff • @AmeMikana Device source & help • @sammyadityant

Signed RenzAlt

Showing the 12 most recent of 20 posts we hold for @RedmiS2IndonesiaChannel. 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 — 888,505 of 1,189,255entries 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

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

“Redmi S2 Indonesia Channel” (@RedmiS2IndonesiaChannel), 1,055 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/RedmiS2IndonesiaChannel.

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.