Telegram RegisterThe public register of Telegram
Telegram profile photo for Prayers Club πŸ™

Channel

Prayers Club πŸ™

@prayers_club

On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Cite this entry

69subscribers

-3 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-1002173901981
TypeChannel
Username@prayers_club
CreatedBetween 1 June 2024 and 1 August 2024 β€” estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live2 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/prayers_club

Topic

Crypto & trading β€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 66% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured β€” it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

697270.57 August 2026 β€” 72 subscribers9 August 2026 β€” 72 subscribers8 September 2026 β€” 70 subscribers2 October 2026 β€” 69 subscribers7 August 20262 October 2026
4 measurements spanning 56 days, net -3. 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 69–72 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 05:5869-1
8 Sept 2026, 00:5870-2
9 Aug 2026, 22:4772no change
7 Aug 2026, 13:0972first reading

Engagement

20 posts held, back to 1 August 2024 β€” 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 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 13 August 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

307 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 42.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ™13042.3%
❀7223.5%
πŸ”₯6019.5%
πŸ‘Œ113.58%
✍103.26%
πŸ’©103.26%
πŸ’…92.93%
🀝51.63%

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 18 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 307 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 1 August 2024 to 13 August 2024, 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

13 Aug 2024, 14:51 UTC853 views31 reactionsread 9 August 2026
Photo

The lock icon on our liquidity has finally appeared after 7 days of persistence and countless messages to support. πŸ”’ Confirming the liquidity is burned and locked. πŸ”₯ For those who doubted us and thought we were faking it, the proof is now undeniable. Our liquidity is safu and untouchable. $pray with us. πŸ™ p.s. also don't forget the ongoing photo contest for those who can imagine and create on @base

πŸ™16❀9πŸ”₯6

9 Aug 2024, 16:24 UTC784 views21 reactionsread 9 August 2026
Photo

https://x.com/prayers_club/status/1821575889701777445 πŸ™πŸ™πŸ™ For our early adopters, we want to take some marketing steps today and tell you what the devs cult are praying for. The $PRAY Token App enables users to create and join prayer topics, supporting each other by contributing $PRAY tokens. Prayers can engage with the app by creating or joining topics, viewing trending and historical topics, managing their wall…

πŸ™10πŸ”₯6❀5

7 Aug 2024, 11:19 UTC625 views16 reactionsread 9 August 2026
Photo

https://warpcast.com/~/channel/prayersclub

❀6πŸ”₯5πŸ™3πŸ’…2

7 Aug 2024, 05:24 UTC513 views10 reactionsread 9 August 2026

Our TG chat, in case someone was looking for. @prayers_chat

❀6✍2πŸ™2

5 Aug 2024, 19:59 UTCβ‰ˆ1,550 views27 reactionsread 9 August 2026
Photo

BY THE WAY, WE’VE COMPLETELY BURNED OUR LP TOKENS πŸ™ https://basescan.org/token/0x4d5313420470239460a977E4E89C4C27043eaA1e IT’S TIME TO $PRAY πŸ™ https://x.com/prayers_club/status/1820549745364041754

πŸ”₯13❀6πŸ™5🀝3

5 Aug 2024, 18:57 UTC545 views16 reactionsread 9 August 2026
Photo

$PRAY WAS OFFICIALLY VERIFIED ON DEXSCREENER GO SUPPORT US WITH πŸš€ https://dexscreener.com/base/0x4d5313420470239460a977e4e89c4c27043eaa1e WE ARE JUST GETTING STARTED, $PRAY TUNED FOR ROADMAP πŸ™

πŸ”₯9πŸ™4❀3

5 Aug 2024, 18:49 UTC437 views12 reactionsread 9 August 2026
Photo

πŸ™ a friendly reminder to NFT holders to claim their early user rewards here: https://beliefs.social/0xE41DE0C5694FC7d995cac53Ae3f8fb91c7aDe692 REWARDS button πŸ™

πŸ™6πŸ”₯3❀2🀝1

5 Aug 2024, 16:26 UTC371 views12 reactionsread 9 August 2026

our tg chat: @prayers_chat

πŸ”₯5πŸ™3πŸ’…2πŸ’©2

5 Aug 2024, 16:14 UTC373 views14 reactionsread 9 August 2026
Photo

SEND THE ROCKET https://dexscreener.com/base/0x4d5313420470239460a977e4e89c4c27043eaa1e

πŸ™7❀3πŸ’©3πŸ”₯1

5 Aug 2024, 16:10 UTC328 views14 reactionsread 9 August 2026

https://app.uniswap.org/swap?outputCurrency=0xE41DE0C5694FC7d995cac53Ae3f8fb91c7aDe692&chain=base OFFICIAL UNI LP LINK

πŸ™6πŸ’©4❀2πŸ”₯2

5 Aug 2024, 16:03 UTC311 views13 reactionsread 9 August 2026

GO BUY ON UNI https://dexscreener.com/base/0x4d5313420470239460a977e4e89c4c27043eaa1e CA: 0xE41DE0C5694FC7d995cac53Ae3f8fb91c7aDe692

πŸ™9❀2πŸ’©1🀝1

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

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 2 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œPrayers Club πŸ™β€ (@prayers_club), 69 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/prayers_club.

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.