Telegram RegisterThe public register of Telegram

Channel

雨过天晴

@MaoDlecat

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

1,457subscribers

+129 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003848855167
TypeChannel
Username@MaoDlecat
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/MaoDlecat

Growth

1,3281,4571,392.56 August 2026 — 1,328 subscribers7 August 2026 — 1,341 subscribers9 August 2026 — 1,438 subscribers13 August 2026 — 1,457 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +129. 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 1,309–1,476 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:451,457+19
9 Aug 2026, 23:341,438+97
7 Aug 2026, 00:271,341+13
6 Aug 2026, 08:361,328first reading

Engagement

20 posts held, back to 22 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
37.4%
avg views ÷ 1,457 subscribers
Avg views / post
546
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
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 6 August 2026
Posts held20 (22 July 20266 August 2026)
Views total10,912
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 08:36 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.

Recent posts

4 Aug 2026, 20:33 UTC≈117 viewsread 6 August 2026

2992222xx 12u 2992222xx 12u 2992222a2 10u sold out 2992222xx 12u 2992222aa 13u sold out

Signed 哈基米互推

4 Aug 2026, 09:51 UTC≈146 viewsread 6 August 2026

万般努力只为出人头地低头弯腰只为爬的更高

Signed 哈基米互推

4 Aug 2026, 09:50 UTC≈147 viewsread 6 August 2026
Video

Video, posted without a caption

Signed 哈基米互推

2 Aug 2026, 19:50 UTC≈210 viewsread 6 August 2026

📱📱📱V信系列📱📱📱 满月实名带支付85U(包秒带资料) 半年实名带支付125U(包秒带资料) 年号实名带支付145U(包秒带资料) 售后:包秒 包首登五分钟 包十五天找回 📱冻结支付📱 满月冻结支付70U(包秒带资料) 年号冻结支付90U(包秒带资料) 3-8年老号死密带账单 100U (包秒带资料) 售后:包秒 包首登五分钟 包十五天找回 📱其他📱 无视扫码可根据客户要求修改资料 75U 国内无视18带身份证正反支付 90U 二月护照实名冻结 80U 售后:包秒 包首登五分钟 包十五天找回 📱香港澳门马来西亚各国V信都有详细清联系客服 📱📱📱快手系列📱📱📱 快手首次留卡两天 7U 快手百粉真人粉 30U 快手三百到五百真人粉 55U 快手千粉真人粉 65U 快手万粉真人粉 210U 快手包首次直播老号 75U (以上快手都是纯私人账号) 售后:包登录 留卡时间内自

1 Aug 2026, 20:20 UTC≈212 viewsread 6 August 2026

👑 32 江苏神父😀😀秒 45 广西神父😀😀秒 46 海南神父😀😀秒 13 河北个户 😀😀秒 43 湖南神父 😀😀秒 65 新疆神父 😀😀秒 41 河南社保 😃😀秒 37 山东神父 😃😀秒 42 湖北神父 😀😀秒 36 江西单头 😀😀秒 50 重庆个户 😃😀秒 34 安徽个户 😃😀秒 36 江西神父 😃😀秒 44 广东神父 😃😀秒 @fox_caller

31 Jul 2026, 20:10 UTC≈1,140 viewsread 6 August 2026
Photo

哈🐔米互推效果【免费互推不收取任何费用】 一天最少进30人

31 Jul 2026, 11:13 UTC≈438 viewsread 6 August 2026
Photo

🤞展示互推效果【免费互推不收取任何费用】 一天最少进30人 参加互推联系 @fox_caller

Signed 哈基米互推

Showing the 12 most recent of 20 posts we hold for @MaoDlecat. 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 — 170,491 of 1,345,403entries 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.

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

“雨过天晴” (@MaoDlecat), 1,457 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/MaoDlecat.

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.