Telegram RegisterThe public register of Telegram
Telegram profile photo for Miko CI Builds

Channel

Miko CI Builds

@MikoCIBuilds

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

24,363subscribers

+1,192 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002720936730
TypeChannel
Username@MikoCIBuilds
Description聊天 @MikoChatGroup 通知 @wsy666HD 日志 @MikoChatGroup_Log 没钱自会各奔东西
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/MikoCIBuilds

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 65% 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.

Views per post sit far above this size band

14,800 average views per post against 24,363 subscribers — an engagement rate of 60.7%. Across the 1,358 registered channels in the same cohort — 10,026–31,616 subscribers, posting mainly in Chinese — the middle half sit between 1.51% and 7.83%, with a median of 3.34%.

What this was computed from
Window30 days (28 August 2026 – 27 September 2026)
Posts measured15 of 19 published in the window (0 exact, 15 rounded by Telegram)
Views totalled221,990
Mature posts only64.5% over 14 posts read at least 24h after publication
Subscribers24,363 measured 25 September 2026
Cohortb10000:zho · 1,358 channels · p10 0.448% · p25 1.51% · p50 3.34% · p75 7.83% · p90 14.8%
Position in cohort99.337th percentile · 18.2× the cohort median
Uncertainty±0.041% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 27 September 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.

Growth

23,17124,36323,7677 August 2026 — 23,171 subscribers8 August 2026 — 23,206 subscribers9 August 2026 — 23,252 subscribers10 August 2026 — 23,277 subscribers11 August 2026 — 23,305 subscribers12 August 2026 — 23,323 subscribers13 August 2026 — 23,335 subscribers14 August 2026 — 23,365 subscribers16 August 2026 — 23,408 subscribers17 August 2026 — 23,437 subscribers18 August 2026 — 23,501 subscribers19 August 2026 — 23,559 subscribers20 August 2026 — 23,616 subscribers21 August 2026 — 23,652 subscribers23 August 2026 — 23,675 subscribers25 August 2026 — 23,724 subscribers25 August 2026 — 23,749 subscribers27 August 2026 — 23,766 subscribers28 August 2026 — 23,790 subscribers29 August 2026 — 23,813 subscribers30 August 2026 — 23,846 subscribers31 August 2026 — 23,876 subscribers1 September 2026 — 23,893 subscribers2 September 2026 — 23,905 subscribers3 September 2026 — 23,960 subscribers5 September 2026 — 24,014 subscribers8 September 2026 — 24,086 subscribers11 September 2026 — 24,128 subscribers13 September 2026 — 24,188 subscribers14 September 2026 — 24,216 subscribers16 September 2026 — 24,245 subscribers19 September 2026 — 24,280 subscribers25 September 2026 — 24,363 subscribers7 August 202625 September 2026
33 measurements spanning 49 days, net +1,192. 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 22,992–24,542 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 13:5924,363+83
19 Sept 2026, 02:1824,280+35
16 Sept 2026, 13:4124,245+29
14 Sept 2026, 18:1524,216+28
13 Sept 2026, 03:3724,188+60
11 Sept 2026, 07:0124,128+42
8 Sept 2026, 14:2224,086+72
5 Sept 2026, 08:0124,014+54
3 Sept 2026, 08:3323,960+55
2 Sept 2026, 00:5423,905+12
1 Sept 2026, 03:0523,893+17
31 Aug 2026, 02:4523,876+30
30 Aug 2026, 03:1923,846+33
29 Aug 2026, 00:1723,813+23
28 Aug 2026, 00:2723,790+24
27 Aug 2026, 02:3823,766+17
25 Aug 2026, 23:3923,749+25
25 Aug 2026, 00:0423,724+49
23 Aug 2026, 08:4723,675+23
21 Aug 2026, 22:3523,652first reading

Engagement

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

ERR · 30 days
60.7%
avg views ÷ 24,363 subscribers
Avg views / post
14,800
15 posts measured
Reaction rate
0.335%
reactions ÷ views · ER floor
Posts in window
19
of 31 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 26 September 2026
Posts held31 (7 July 2026 – 26 September 2026)
Views total221,990
Reactions total744
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Sept 2026, 23:45 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
42
Videos
1
Links
30

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

1,610 reactions across 27 posts, in 7 distinct kinds. The most used accounts for 54.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍88154.7%
❤40425.1%
😭1116.89%
🤔1026.34%
🗿714.41%
👏241.49%
😘171.06%

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

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

26 Sept 2026, 15:09 UTC≈1,870 views116 reactionsread 26 September 2026
Photo

后续不再启用QQ/Telegram聊天组

😭77👍28🤔8👏2❤1

Signed k0nf1g

22 Sept 2026, 08:51 UTC≈8,300 views62 reactionsread 26 September 2026
File

File, posted without a caption

👍51❤5😘4🤔2

Signed k0nf1g

21 Sept 2026, 03:32 UTC≈9,300 views30 reactionsread 26 September 2026

出微信-Ipad全协议 有意者私联 @fuuckeveryone

👍25🗿5

Signed k0nf1g

17 Sept 2026, 14:18 UTC≈13,800 views24 reactionsread 26 September 2026

新抖音去水印 https://qsy.guang233.com/ 源代码 https://github.com/dartcv/qsyTool

👍19❤5

Signed k0nf1g

17 Sept 2026, 03:15 UTCviews —

Miko CI Builds pinned «接各种逆向 正向 联系 @fuuckeveryone 直接报需求和预算»

17 Sept 2026, 03:04 UTC≈13,800 views12 reactionsread 26 September 2026

接各种逆向 正向 联系 @fuuckeveryone 直接报需求和预算

👍11❤1

14 Sept 2026, 14:37 UTC≈16,200 views63 reactionsread 26 September 2026
File

🔥回来吧我的se🔥 😡我最骄傲的信仰😡 🥰历历在目的脚本🥰 😭眼泪莫名在流淌😭 😥依稀记得机器人😥 🤗还有你给的外显🤗 🤓让小学生们崇拜🤓

👍52❤7🤔4

Signed k0nf1g

13 Sept 2026, 13:50 UTC≈16,600 views41 reactionsread 26 September 2026
File

解决了一些有问题的用户 你过得好我才能恨你,你过得不好,我都不知道自己该恨你还是抱住你。

👍34❤5🤔1😘1

Signed k0nf1g

11 Sept 2026, 13:51 UTC≈15,000 views41 reactionsread 26 September 2026
File

解决了一些已知的问题

👍35🗿6

Signed k0nf1g

10 Sept 2026, 13:44 UTC≈17,700 views72 reactionsread 26 September 2026
File

微信功能增强模块(最终测试版) 如何使用: 在LSPosed框架(几乎所有Xposed框架都行)内勾选Nuke并选择微信作为作用域,随后长按微信将其强制停止,打开微信设置后会即可配置功能 常见问题: 出现"Dex分析失败:NameNotFoundException"时,请配置你的hide-my-applist使其不对微信隐藏Nuke,随后重启 出现"Dex分析失败:IllegalStateException"时,可能是设备无法从服务器下载运行文件,尝试连接VPN后继续 注意: 抖音,QQ作用域功能有限,不推荐勾选,推荐使用微信8.0.76,请不要在国内平台分享哦,包括酷安☺️ @MikoCIBuilds 谢谢支持 @MikoChatGroup 获取帮助 微信8.0.76下载 https://dldir1v6.qq.com/weixin/android/weixin8076android3141_0x28004c31_arm64.…

👍48❤22😘2

Signed k0nf1g

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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

“Miko CI Builds” (@MikoCIBuilds), 24,363 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/MikoCIBuilds.

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.