27 measurements spanning 31 days, net +790. 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 24,448–25,475 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
7 Sept 2026, 16:58
25,356
+54
4 Sept 2026, 18:56
25,302
+23
3 Sept 2026, 06:08
25,279
+10
2 Sept 2026, 00:15
25,269
+9
1 Sept 2026, 02:18
25,260
+40
31 Aug 2026, 00:57
25,220
+15
30 Aug 2026, 03:44
25,205
+42
29 Aug 2026, 02:19
25,163
+16
28 Aug 2026, 05:42
25,147
+31
27 Aug 2026, 04:47
25,116
+21
26 Aug 2026, 02:16
25,095
-7
25 Aug 2026, 05:27
25,102
+10
24 Aug 2026, 06:43
25,092
+30
22 Aug 2026, 15:07
25,062
+33
21 Aug 2026, 07:03
25,029
+9
20 Aug 2026, 07:34
25,020
+44
19 Aug 2026, 09:07
24,976
+27
18 Aug 2026, 10:25
24,949
+36
17 Aug 2026, 10:33
24,913
+34
15 Aug 2026, 16:58
24,879
first reading
Engagement
390 posts held, back to 6 August 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 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
5.23%
avg views ÷ 25,356 subscribers
Avg views / post
1,330
243 posts measured
Reaction rate
0.209%
reactions ÷ views · ER floor
Posts in window
332
of 390 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. It is computed over the 205 of 243 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 3 September 2026
Posts held
390 (6 August 2026 – 3 September 2026)
Views total
322,483
Reactions total
574
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 10:34 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
Video runtime
1m 09s
Average length
3s
Measured directly from 21 videos 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
658 reactions across 230 posts, in 22 distinct kinds. The most used accounts for 78.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
517
78.6%
🔥
24
3.65%
👍
20
3.04%
👏
20
3.04%
😱
19
2.89%
🥰
16
2.43%
🤩
8
1.22%
✍
5
0.76%
👀
5
0.76%
🍾
3
0.456%
🎃
3
0.456%
🙏
3
0.456%
⚡
2
0.304%
❤🔥
2
0.304%
🎅
2
0.304%
👨💻
2
0.304%
🤓
2
0.304%
🐳
1
0.152%
😁
1
0.152%
🙈
1
0.152%
2 further kinds
2
0.304%
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 238 of the 390 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 658 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 390 most recent posts we hold, published 6 August 2026 to 3 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.
🚨 𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗥𝗘𝗖𝗛𝗔𝗥𝗚𝗘 𝗡𝗢𝗧𝗜𝗖𝗘 🚨
✅ All orders must be completed within 24 hours.
❌ Pending orders will be automatically cancelled and no refund will be provided.
❕ Follow guides below if your order is still pending to avoid cancellation:
• Double-check order details: Amount / Account Number/ IFSC
• Online payment UPI in Umoney tools
• Submit UTR within 30 minutes after taking order
• Make sure payment UPI is added a…
🚨 𝗦𝗖𝗔𝗠 𝗪𝗔𝗥𝗡𝗜𝗡𝗚 𝗔𝗟𝗘𝗥𝗧 🚨
Scammers may contact you through 🚨:
❌ WhatsApp
❌ SMS
❌ Phone Calls
❌ Telegram Fake Customer Service
❌ Other Social Media Platforms
⚠️ Do NOT share your OTP, password, or personal information with anyone.
✅ UMONEY only have Telegram and official customer service accounts below:
💬 @Umoney_ServiceCS22
💬 @Umoney_ServiceCS33
Always verify the username carefully before replying. Stay Safe.
📣🚨 𝗨𝗠𝗢𝗡𝗘𝗬 𝗥𝗘𝗖𝗛𝗔𝗥𝗚𝗘 𝗧𝗜𝗣𝗦 – 𝗥𝗘𝗔𝗗 𝗕𝗘𝗙𝗢𝗥𝗘 𝗬𝗢𝗨 𝗣𝗔𝗬 🚨📣
To avoid pending status or failed orders, please follow these important steps when placing order:
✅ 1. Tools must be ONLINE & ACTIVE
✅ 2. Ensure tools are linked to your User ID
⏰ 3. Submit UTR within 30 minutes taking order
🧾 4. Double check details: ORDER AMOUNT / ACCOUNT NUMBER / IFSC
🔔 Always make sure your UPI ID is RUNNING in UMONEY
Following these steps will…
❕ 𝗖𝗨𝗦𝗧𝗢𝗠𝗘𝗥 𝗦𝗘𝗥𝗩𝗜𝗖𝗘 𝗡𝗢𝗧𝗜𝗖𝗘 ❕
👉 When contacting customer service for the first time, please type and send your UMONEY User ID in the message.
❌ Do not send screenshots only, as we may be unable to locate your account.
━━━━━━━━━━━━━━━
🏦 Customer Support 🏦
📱 @Umoney_ServiceCS22
📱 @Umoney_ServiceCS33
🏦 Official Website 🏦
📱 https://www.umoneyindia.com/
🚨 𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗥𝗘𝗖𝗛𝗔𝗥𝗚𝗘 𝗡𝗢𝗧𝗜𝗖𝗘 🚨
✅ All orders must be completed within 24 hours.
❌ Pending orders will be automatically cancelled and no refund will be provided.
❕ Follow guides below if your order is still pending to avoid cancellation:
• Double-check order details: Amount / Account Number/ IFSC
• Online payment UPI in Umoney tools
• Submit UTR within 30 minutes after taking order
• Make sure payment UPI is added a…
🚨 𝗡𝗘𝗪 𝗦𝗖𝗔𝗠 𝗔𝗟𝗘𝗥𝗧 🚨
Scammers are impersonating UMoney Customer Service and asking users to share their WhatsApp screen to steal OTPs.
❕ UMoney support is ONLY available on Telegram via:
✅ @Umoney_ServiceCS22
✅ @Umoney_ServiceCS33
❌ Ignore all WhatsApp messages, phone calls, or any other Telegram IDs claiming to be UMoney Support.
Never share your screen. Never share your OTP.
❤1
Showing the 12 most recent of 390 posts we hold for @UMoney_Wallet_Official. 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 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.
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 7 September 2026 — this
entry's latest reading, not the date you are reading this.
“Umoney Wallet” (@UMoney_Wallet_Official), 25,356 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/UMoney_Wallet_Official.
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.