Telegram RegisterThe public register of Telegram
Telegram profile photo for Mithka CI

Channel

Mithka CI

@mithka_ci

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

141subscribers

+4 since we began measuring on 29 September 2026

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

Register entry

Telegram ID-1003941085891
TypeChannel
Username@mithka_ci
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live14 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 October 2026
On Telegramt.me/mithka_ci

Topic

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

Growth

13714113929 September 2026 — 137 subscribers29 September 2026 — 137 subscribers5 October 2026 — 140 subscribers14 October 2026 — 141 subscribers29 September 202614 October 2026
4 measurements spanning 14 days, net +4. 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 136–142 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 01:47141+1
5 Oct 2026, 08:56140+3
29 Sept 2026, 19:22137no change
29 Sept 2026, 18:48137first reading

Engagement

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

ERR · 30 days
53.6%
avg views ÷ 141 subscribers
Avg views / post
75.6
10 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
10
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 25 September 2026
Posts held20 (1 September 2026 – 25 September 2026)
Views total756
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Sept 2026, 19:22 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

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.0%

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 3 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 3 reactions 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 1 September 2026 to 25 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

25 Sept 2026, 04:06 UTC50 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.6.1-nightly.20260925.7bcb7fc · 20260925 Summary: English: • Video playback is now scoped to the source account, so videos in chats and moments stay tied to the right account and context. • Desktop keyboard shortcuts are now kept local to Mithka and preserved across search and input surfaces while keeping platform shortcuts available. • The desktop title bar now shows status and includ…

24 Sept 2026, 07:16 UTC61 viewsread 29 September 2026

🚀 Mithka release v1.5.5 · 20260924 Downloads: https://github.com/iebb/mithka/releases/tag/v1.5.5

23 Sept 2026, 04:00 UTC63 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.5.4-nightly.20260923.425fe98 · 20260923 Summary: English: • Video playback is more stable after seeking, avoiding stalled playback when interrupted ranges are abandoned. • Video playback failures are reported more clearly, and Android video plugin registration has been restored for better reliability. • Message links are now separated from bubble text so links and text formatting are …

22 Sept 2026, 03:58 UTC54 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.5.3-nightly.20260922.654b51d · 20260922 Summary: English: • Quote selected desktop message text in place for clearer replies and context. • Improved chat bubbles, action menus, and media album layouts for smoother message quoting and display. 中文: • 桌面端现在可直接在原位置引用选中的消息文本,便于回复并保留上下文。 • 优化了聊天气泡、操作菜单和媒体相册布局,使引用和消息展示更加顺畅。 Downloads: https://github.com/iebb/mithka/releases/tag/v1.5.3-night…

21 Sept 2026, 03:57 UTC67 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.5.2-nightly.20260921.6f029fc · 20260921 Summary: English: • Unread chat history paging now stays in place instead of jumping to the latest messages. • Replying to messages now supports partial quote selections, making it easier to quote the exact text you want. • Archived chat actions on macOS now use the desktop row actions for a more consistent experience. • Automatic day and night …

20 Sept 2026, 04:04 UTC186 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.5.1-nightly.20260920.8f1415f · 20260920 Summary: English: • Improved navigation across iOS, desktop, and Duo with glass tabs, side navigation, chat folder icons, folder editing, and preserved content layouts. • Moments posts can now display music and stickers. • Added spoiler covers for media with explicit reveal controls. • Fixed media caption bubbles growing wider than their preview…

18 Sept 2026, 08:48 UTC75 viewsread 29 September 2026

🚀 Mithka release v1.4.10 · 20260918 Downloads: https://github.com/iebb/mithka/releases/tag/v1.4.10

18 Sept 2026, 04:02 UTC70 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.4.9-nightly.20260918.a465899 · 20260918 Summary: English: • Moments now supports short videos and animations without requiring thumbnails. • Moments restores your previous content and keeps the visible post when you reopen it. • You can drag images into the targeted chat on macOS. • Added an opt-in liquid glass bottom navigation bar with a more consistent pill-shaped design. 中文: • 动态现…

16 Sept 2026, 03:58 UTC68 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.4.8-nightly.20260916.339e8b5 · 20260916 Summary: English: • Improved custom emoji loading so failed packs retry properly instead of leaving the picker empty until restart. • The add-text dialog now uses the correct cancel label in the editor. • Video playback now streams complete ranges in chunks for smoother, more reliable viewing. 中文: • 改进自定义表情加载,确保表情包加载失败后会重试,而不是让表情选择器一直为空直到重启。 • 编…

15 Sept 2026, 04:00 UTC62 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.4.7-nightly.20260915.07566b8 · 20260915 Summary: English: • Swipe to unarchive chats directly from the archived chats list. • Search submissions now preserve scoped searches and media filters. • QR scanning more reliably recovers camera permissions and resumes correctly after returning to the foreground. • Voice recording fallback timers now continue advancing correctly. • Login count…

11 Sept 2026, 03:38 UTC91 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.4.6-nightly.20260911.9fa1413 · 20260911 Summary: English: • Added a video compatibility option for Android, enabled by default to improve playback compatibility. 中文: • 新增安卓视频兼容性选项,默认启用以提升播放兼容性。 Downloads: https://github.com/iebb/mithka/releases/tag/v1.4.6-nightly.20260911.9fa1413

10 Sept 2026, 03:44 UTC77 viewsread 29 September 2026

🚀 Mithka nightly pre-release v1.4.5-nightly.20260910.3cbe5e2 · 20260910 Summary: English: • Improved unread message scrolling so you can jump to unread items more reliably in chats. • Fixed Android media handling for smoother image and video playback in chat. • Resolved download ownership issues so downloaded files are attributed correctly and open more reliably. • Refined chat media previews, transcripts, and momen…

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

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

“Mithka CI” (@mithka_ci), 141 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/mithka_ci.

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.