Telegram RegisterThe public register of Telegram
Telegram profile photo for Muichiro's Build

Channel

Muichiro's Build

@muichirobuilds

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

267subscribers

+6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003540805875
TypeChannel
Username@muichirobuilds
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/muichirobuilds

Growth

2612672646 August 2026 — 261 subscribers7 August 2026 — 261 subscribers7 August 2026 — 262 subscribers14 August 2026 — 267 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +6. 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 260–268 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:38267+5
7 Aug 2026, 02:55262+1
7 Aug 2026, 01:03261no change
6 Aug 2026, 18:47261first reading

Engagement

13 posts held, back to 8 July 2026the 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
105.5%
avg views ÷ 267 subscribers
Avg views / post
282
8 posts measured
Reaction rate
3.77%
reactions ÷ views · ER floor
Posts in window
8
of 13 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 3 August 2026
Posts held13 (8 July 20263 August 2026)
Views total2,254
Reactions total85
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01:03 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

129 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4938.0%
🔥2821.7%
👍1914.7%
😢118.53%
🤷‍♂96.98%
😭75.43%
👏21.55%
🤔21.55%
🥰21.55%

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

Measured over the 13 most recent posts we hold, published 8 July 2026 to 3 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

3 Aug 2026, 08:29 UTC93 views7 reactionsread 7 August 2026
Forwarded from @voltageosannouncementsPhoto

Who ordered something hot? We’ve been quiet lately, but for a good reason... Voltage OS 6.0 is coming this month! August is going to be packed with surprises, performance gains, and a whole new level of smoothness. Mark your calendars, See you soon 😉 @VoltageOS

🔥52

30 Jul 2026, 15:59 UTC319 views10 reactionsread 7 August 2026

https://artifacts.serverhive.in/?id=axion-aosp-surya-20260729-115645730545 There you go FYI - no reporting of bugs if encountered since source is not officially released yet

🔥52👏2👍1

30 Jul 2026, 09:31 UTC300 views5 reactionsread 7 August 2026

Should i share the link here?? Since some users are interested

👍32

29 Jul 2026, 11:35 UTC325 views12 reactionsread 7 August 2026
Photo

Axion OS Private Build😂

6🔥3🤔2👍1

29 Jul 2026, 06:09 UTC180 views17 reactionsread 7 August 2026
Forwarded from @InfinityXUpdatePhoto

New Release of Project Infinity X v3.12 for POCO X3 NFC (surya) is Up! By Muichiro Tokito ▫️ Variants: GAPPS & Vanilla ▫️ Size: 1.95 GB (Vanilla) | 2.27 GB (Gapps) ▫️ Date: 29th July 2026 ⭐ Wanna have a look at some ROM Screenshots? - Click Here 💬 Reach Support If have any queries - Click Here #Android16 #surya @ProjectInfinityX

🔥113👍3

25 Jul 2026, 23:36 UTC229 views8 reactionsread 7 August 2026
Forwarded from @ProjectInfinityX

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 26/07/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

8

22 Jul 2026, 00:13 UTC486 views17 reactionsread 7 August 2026

Sadly my device's display died, a17 bring up will be paused until my display is fixed😬

😢11😭5👍1

14 Jul 2026, 11:02 UTC608 views6 reactionsread 7 August 2026
Forwarded from @voltageosannouncementsPhoto

We want to expand our official support and make VoltageOS available across a wider range of devices, but we need your help to make it happen. To make it easier for passionate developers to join the team, we have relaxed our application requirements. If you have been independently maintaining the ROM for your device for at least a month and have achieved stable builds, you are now fully eligible to apply for official

6

9 Jul 2026, 02:58 UTC≈1,120 views9 reactionsread 7 August 2026
Photo

#Voltage #Unofficial #ROM #BKA #Surya #Karna Voltage OS v5.11 EOL - Unofficial | Android 16 QPR2 Updated: 8/07/26 ▪️ Download : ROM ▪️ Screenshot : Here ▪️ Recovery : Here Changelog: * July Patch * Include Dolby & Leica * Misc changes and improvements Notes: • Use Latest FW • Vanilla Build - Use mindthegapps • For best experience - turn off window level blur on display settings to disable blur and let the phone s

6😭2🔥1

Showing the 12 most recent of 13 posts we hold for @muichirobuilds. 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 — 459,130 of 1,481,502entries 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.

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.

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

“Muichiro's Build” (@muichirobuilds), 267 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/muichirobuilds.

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.