一周过去了无事发生,大概率是好了🍾
🎉10💋1

Channel
@Howards_mumbles
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
699subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001220527471 |
|---|---|
| Type | Channel |
| Username | @Howards_mumbles |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/Howards_mumbles |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 13:00 | 699 | no change |
| 7 Aug 2026, 09:33 | 699 | first reading |
19 posts held, back to 27 May 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (27 May 2026 – 6 August 2026) |
| Views total | 2,724 |
| Reactions total | 70 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 09:33 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.
172 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 33.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 58 | 33.7% | |
| 😇 | 38 | 22.1% | |
| 👍 | 19 | 11.0% | |
| 🥰 | 14 | 8.14% | |
| ❤ | 12 | 6.98% | |
| 🎉 | 10 | 5.81% | |
| 🤯 | 10 | 5.81% | |
| 😱 | 6 | 3.49% | |
| 😁 | 4 | 2.33% | |
| 💋 | 1 | 0.581% |
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 15 of the 19 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 172reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 27 May 2026 to 6 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.
一周过去了无事发生,大概率是好了🍾
🎉10💋1
又发作了,考虑是荨麻疹 换药 其他全停换盐酸西替利嗪片 痒啊😇 找不到过敏原,可能是前天熬夜到4点多免疫系统跟我爆了😇
😇16
稍微熬一下夜就坏掉了 昨天全身过敏起疹子 吃了各种抗过敏药比如氯雷他定、马来酸氯苯那敏和地塞米松还有钙片还有涂了一大堆醋酸地塞米松软膏 然后今天就一直打嗝打嗝😇 然后今天疹子还是会一点点冒出来,虽然问题不大但是真的很痒 各位还是不要熬夜了
😇13
发现早上起床量身高和晚上量竟然差距高达 2cm
🤯10
杂鱼病毒 看我免疫系统4天清除你
🔥20
小米电视5 65寸 root 成功跑起来 LSPosed
🔥38😁1
发现这种情况下不能用通行密钥是因为在超级省电模式下被禁用的 Play 服务在退出之后重新自动启用后,它的通行密钥服务不自动恢复,需要手动到设置里选择首选服务为其他再设置回来重新激活 这里不知道是谁的锅,小米的锅在超级省电禁用 Play 服务然后退出后不恢复通行密钥服务,谷歌的锅在设置存储里面首选服务在 Play 服务被禁用后是不清除的,但是实际上服务被禁用了,然后重新启用应用又没有启用服务,导致设置显示的和实际情况不一致
😇9
退出账号之后登录一次就好了,这个时候会发现登录并未成功,需要再登录一次 可第一次是先解除锁定,再登录一次才真正能登录 这个问题非常奇怪,在网页修改 Gmail 地址之后,手机上账号与同步那里的地址也是同步更新的,登录状态不掉,能正常在 Play 商店安装和更新应用,只不过系统认为不是同一个账号然后触发 FRP,可是都没有恢复出厂设置这一步
🥰9
谷歌账号支持修改 Gmail 账号之后,试了一下修改,竟然触发了 Android 设备的 FRP (Factory Reset Protection) 导致无法侧载应用 在一台设备上不知道怎么点几下自己好了,在另一台设备上怎么都解除不了
肠粉 自制了酱汁,配料只有酱油、白糖、松茸鲜、蒜蓉和水
👍12
原本的意思回来了
❤1
发现有群用机器人整体冒充整个群的成员的头像和昵称并批量发言来增加群聊活跃度 如果发现有熟悉的头像和昵称的群友在某些奇奇怪怪的群一直重复几句话就可以认为被假冒了
Showing the 12 most recent of 19 posts we hold for @Howards_mumbles. 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 — 431,220 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.
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.
Named by 2 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Howard's 碎碎念” (@Howards_mumbles), 699 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Howards_mumbles.
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.