Telegram RegisterThe public register of Telegram
Telegram profile photo for MetaKuma

Channel

MetaKuma

@KumaTea

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

115subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001454145827
TypeChannel
Username@KumaTea
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/KumaTea

Growth

1131151147 August 2026 — 114 subscribers9 August 2026 — 114 subscribers16 August 2026 — 113 subscribers23 August 2026 — 114 subscribers30 August 2026 — 115 subscribers7 August 202630 August 2026
5 measurements spanning 22 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 113–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 00:44115+1
23 Aug 2026, 10:16114+1
16 Aug 2026, 03:03113-1
9 Aug 2026, 06:00114no change
7 Aug 2026, 21:44114first reading

Engagement

20 posts held, back to 3 June 2023the 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.

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 21 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 18s
Average length
2m 18s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

3 reactions across 2 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
133.3%
🤩133.3%
🥰133.3%

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 7 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 3 June 2023 to 21 July 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

21 Jul 2026, 17:04 UTC106 viewsread 9 August 2026

github.com/KumaTea/homir 通过 Vibe Coding 完全未参与编程 制作的第一个中型项目

Signed Kuma Tea

21 Jul 2026, 17:02 UTC59 viewsread 9 August 2026

github.com/KumaTea/janews 初次尝试 Vibe Coding 制作的第一个小项目

Signed Kuma Tea

15 Jan 2026, 04:28 UTC297 viewsread 9 August 2026

新项目:harmonyos-eco-practice 主播之前为了尝试新鲜事物以及折腾折磨自己买了一个哇维平板 体验了一个月左右,生态确实非常贫瘠 所以开个坑,逐渐把找到的替代方案写进去

Signed Kuma Tea

18 Mar 2024, 23:24 UTC596 views2 reactionsread 9 August 2026
Forwarded from @KumaSpaceVideo

新项目 ⭕😇双语字幕 GI-Subtitles 的性能+功能改进版 非原创,但爆肝两天完全重写 已开源 genshin-dual-sub 暂时没做一键安装包,有人点⭐再做

🤩1🥰1

Signed Kuma Tea

14 Mar 2024, 08:41 UTC592 viewsread 9 August 2026

KumaTea / ext-whl pip config set global.extra-index-url https://ext.kmtea.eu/simple 谢谢喵

Signed Kuma Tea

10 Mar 2024, 16:48 UTC529 viewsread 9 August 2026

两个不重要的小公告 1. 明日搬迁土豆服务器,预计本地运行的 bot (如 @rbevbot) 将会下线,预计至多掉线24小时。 2. 我的项目最近更换了服务条款。如果你是 qljj,请 点击此链接 ;如果是 g/f2d,请 点击此链接。点击后可能需要再点一次下方的 start 按钮。如果你都不是,则无需操作。

Signed Kuma Tea

29 Feb 2024, 17:17 UTC434 viewsread 9 August 2026

摸了新 Bot @hisrchbot 由于 Telegram 官方迟迟不愿添加东亚文字搜索支持,以至于有些第三方客户端都自己加上了 我有这个想法很久了,今天一鼓作气写了出来,bug以后慢慢修吧

Signed Kuma Tea

15 Feb 2024, 11:47 UTC433 viewsread 9 August 2026

摸了新 Bot @rmTrackBot 使用 Inline 方式,贴上网址 (只要包含就可以 比如从B站直接复制出来的) 即可净化链接 注:适用于B站等,无法用于绝大部分需要 id 参数找到帖子的论坛

Signed Kuma Tea

28 Jan 2024, 05:55 UTC463 views0 reactionsread 9 August 2026

两个不重要的小公告 1. 我的机场今日到期,预计春节有活动才会续费,届时自动切换到免费的 CF Warp 节点,因此运行在本地的 bot (如 @rbevbot) 响应会有较严重的波动0201已续费 2. 如果部分用户发现被 bot 拒绝服务了,可能是因为是TG大会员

Signed Kuma Tea

6 Jan 2024, 12:17 UTC440 views1 reactionsread 9 August 2026

以后打算在 KumaTea / speedrun 这里更新一些自己的速通经历 不说是教程是因为没有普适性,仅搜集资料、准备方向有些许参考性而已 欢迎围观

1

Signed Kuma Tea

30 Dec 2023, 17:36 UTC414 viewsread 9 August 2026

由于成本问题,以下 bot 预计将在2024年1月初暂停运行,直到我找到低价或免费替代方案: @rbskbot 由于活跃度问题,以下 bot 预计将在2024年1月初关闭,功能后续合并至其他现有bot: @DKJCBot

Signed Kuma Tea

24 Nov 2023, 17:40 UTC473 viewsread 9 August 2026

#新项目 新写的代码执行 bot @rbevbot 目前趋于稳定,欢迎大家试用。 该 bot 是我很喜欢但已跑路的 @rextester_bot 的一个轮子。 目前跑在软路由上,性能受限,仅支持少量语言,一些比较大的语言镜像装不下;但已开源,欢迎大家自行在自己的服务器上配置,如果能点个星就更好了。 (私聊不会有反应,我的一贯做法,只在群聊启用)

Signed Kuma Tea

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

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

“MetaKuma” (@KumaTea), 115 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/KumaTea.

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.