Telegram RegisterThe public register of Telegram
Telegram profile photo for MESSIAH🦋

Channel

MESSIAH🦋

@messiahvvip

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

22,880subscribers

-201 since we began measuring on 22 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001516147019
TypeChannel
Username@messiahvvip
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/messiahvvip

Growth

22,88023,08122,980.522 August 2026 — 23,081 subscribers23 August 2026 — 23,045 subscribers25 August 2026 — 23,053 subscribers26 August 2026 — 23,024 subscribers28 August 2026 — 23,004 subscribers28 August 2026 — 22,986 subscribers30 August 2026 — 23,040 subscribers31 August 2026 — 23,000 subscribers1 September 2026 — 22,966 subscribers2 September 2026 — 22,932 subscribers3 September 2026 — 22,903 subscribers5 September 2026 — 22,880 subscribers22 August 20265 September 2026
12 measurements spanning 14 days, net -201. 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 22,850–23,111 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 02:1822,880-23
3 Sept 2026, 06:1622,903-29
2 Sept 2026, 00:5822,932-34
1 Sept 2026, 03:4522,966-34
31 Aug 2026, 01:3623,000-40
30 Aug 2026, 00:5423,040+54
28 Aug 2026, 23:3322,986-18
28 Aug 2026, 02:4723,004-20
26 Aug 2026, 05:5323,024-29
25 Aug 2026, 03:5823,053+8
23 Aug 2026, 21:0523,045-36
22 Aug 2026, 13:0023,081first reading

Engagement

119 posts held, back to 20 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 30 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.65%
avg views ÷ 22,880 subscribers
Avg views / post
378
117 posts measured
Reaction rate
0.505%
reactions ÷ views · ER floor
Posts in window
119
of 119 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 67 of 117 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held119 (20 August 20263 September 2026)
Views total44,247
Reactions total156
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 12:47 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

156 reactions across 65 posts, in 7 distinct kinds. The most used accounts for 67.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10567.3%
🔥2113.5%
👍95.77%
👏85.13%
53.21%
🙏42.56%
🤯42.56%

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 67 of the 119 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 156 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 119 most recent posts we hold, published 20 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.

Recent posts

3 Sept 2026, 12:46 UTC1 views1 reactionsread 3 September 2026
Photo

🙏 STAKE AS GIVING ✅✅✅ 🤝 I STAKED €300 🔥🔥🔥🔥 #MESSIAH✅

1

3 Sept 2026, 12:08 UTC42 views0 reactionsread 3 September 2026
Photo

Locked games ✅❤️ unlocked it at an offer✅

3 Sept 2026, 07:42 UTC212 views1 reactionsread 3 September 2026
Photo

🚨 TODAY’S VIP PICKS ARE OUT! ⚽🔥 💰 I’ve already placed my £300 stake, and today’s selections are ready to go! 🍀 ⏰ VIP members: Get your bets placed before kickoff and stay active for updates. Not in the VIP yet? Join now and get access to today’s selections before the games start. 🔥 📩 VIP Access: @messiah_guru1 @messiah_guru1 ⚡️ Don’t miss today’s games!

1

3 Sept 2026, 04:43 UTC267 views2 reactionsread 3 September 2026
Photo

✅ VIP Bet Result Locked In! Another victory secured — payouts cleared and delivered! 💸✅ See the proof below! 📸 Stay tuned… the next big win could be yours! 🚀 ⚡️ - @messiah_guru1 @messiah_guru1 @messiah_guru1

👏1🙏1

3 Sept 2026, 04:42 UTC269 views1 reactionsread 3 September 2026
Photo

👁®️ U N C O V E R E D ®️👁 🍀ORIGINAL TICKET OPENED🍀 🍾 £300.00 // £107265.00 🍾 💴🏅Congratulations To All Winners and thanks for the trust all, Play With the best 🤝💥 ♻️Next 100% Fixed Matches Comfirmed.Message Me Now ▊TEXT ▋ADMIN @messiah_guru1 @messiah_guru1

1

2 Sept 2026, 09:08 UTC479 views3 reactionsread 3 September 2026
Photo

⭕TODAY GOLDEN FIXED TICKET⭕ ------------------------------------------------- ✎ - Deal Today [ ⁉️ Odds ] ✎ - Inbox 👉 @messiah_guru1 ✎ - 100% Real information ✎ - Interested Buyers Should Inbox 👉 @messiah_guru1 Contact 👉 @messiah_guru1

1👏1🔥1

2 Sept 2026, 09:02 UTC450 viewsread 3 September 2026
Photo

Won successful🏆💪🏆💪 @messiah_guru1 @messiah_guru1 @messiah_guru1

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

Mentions

Named by 3 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.

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

“MESSIAH🦋” (@messiahvvip), 22,880 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/messiahvvip.

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.