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 13 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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
15 measurements spanning 50 days, net -153. 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 4,199–4,398 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
25 Sept 2026, 23:36
4,222
-36
15 Sept 2026, 09:37
4,258
-4
11 Sept 2026, 08:56
4,262
-7
6 Sept 2026, 08:21
4,269
-9
1 Sept 2026, 23:16
4,278
-18
29 Aug 2026, 22:33
4,296
-8
27 Aug 2026, 02:53
4,304
-5
24 Aug 2026, 03:19
4,309
-16
20 Aug 2026, 16:15
4,325
-9
17 Aug 2026, 16:16
4,334
-12
14 Aug 2026, 01:46
4,346
-17
10 Aug 2026, 15:45
4,363
-11
7 Aug 2026, 07:33
4,374
-1
6 Aug 2026, 23:45
4,375
no change
6 Aug 2026, 23:33
4,375
first reading
Engagement
20 posts held, back to 2 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pages 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 2 April 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
58s
Average length
29s
Measured directly from 2 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
209 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 49.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
104
49.8%
❤
91
43.5%
👏
8
3.83%
🤝
6
2.87%
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 20 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 209 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 2 January 2025 to 2 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Want to Win an iPhone 16 Pro ? 🔥
Here’s your chance! Simply bring new paid subscribers to Bethel App & you could be one of 3 lucky winners! 🎉
💰 More subs = More chances to win!
🔗 More details about this campaign will publish under this tweet.
https://x.com/BethelPlatform/status/1905083221890515363
#Bethel #EarnWithBethel #SaveToEarn
GUESS & WIN FREE USDT! 🎯💰
Think you know where $BECX is headed? Predict its closing price for April 30th & WIN!
🔥 300 USDT up for grabs! The prize pool will be split among all correct predictions!
⏳ Deadline: April 30th, 11:59 PM IST – Don’t miss out!
💬 Drop your guess NOW & secure your chance to win! 👇
#Bethel #BECX #CryptoRewards
WIN FREE USDT – HOLD & EARN! 🚀
💰 $500 Prize Pool – 72HRS ONLY! 💰
🔹 How to Join?
✅ Hold $10 BECX until March 29, 2025, 11:59 PM IST
✅ Comment “Proof” under this post
🏆 5 New Users: $50 each
🏆 10 Existing Users: $25 each
🚀 HOLD $BECX now on MEXC:
https://tinyurl.com/HOLD-BECX
⏳ Act fast – Don’t miss out!
#Bethel #BECX #HoldToWin #MEXC
A great moment with our CEO Craig at the Australian Crypto Conference 2024!
Discussing Bethel’s vision and how it’s shaping the future of secure data storage.
Exciting times ahead! 🌍✨
#Bethel #AusCryptoCon2024 #ZKP
🚨 Our CEO Craig Bricknell will be speaking at the DLT-Enabled Summit by @DECAustralia on Feb 25, 2025!
He’ll be joining the panel on "Data Ownership, Management & Privacy in a Blockchain-Enabled World", exploring how DLT is transforming digital assets, privacy, and secure data management.
https://x.com/BethelPlatform/status/1889958851484733718
Leaked Videos Everywhere… Are Yours Next? 🥵🔥
This Valentine’s, don’t let your private moments go public. Most storage providers can see your files—you just don’t know it.
🔒 Bethel ZKP Storage = 100% Privacy
Even we can’t access your files. Zero-Knowledge Proof (ZKP) technology makes it unhackable.
🚨 Stay safe. Stay private. Get 1GB free & protect what matters.
📲 Try it now!
Android: https://buff.ly/40H0Iql
iOS: h…
Your Data. Your Control. 🫵
No middlemen, no leaks—just pure ZKP security!
Download Bethel ZKP Storage & take control of your files!
📲 Try it now!
Android: https://buff.ly/40H0Iql
iOS: https://buff.ly/3ZZanbj
#Bethel #ZKP #PrivacyMatters
Discover the power of ZKP storage at your fingertips! 😎
Watch our Bethel Mobile App demo and experience seamless, secure data management like never before. Your privacy, simplified. 🚀
https://x.com/i/status/1878268205774311497
#Bethel #Bethelnet #ZKP #zkpStorage #MobileApp
Showing the 12 most recent of 20 posts we hold for @bethelplatform. 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 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.
Handles this channel named that no longer answer
Dead references
11
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
11
vacant every time we have ever looked
@bethelplatform named 11 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@anuraa6 named in 2 posts, 8 August 2026 – 9 August 2026
@chamikakalhara7 named in 2 posts, 8 August 2026 – 9 August 2026
@craigbricknell named in 2 posts, 8 August 2026 – 9 August 2026
@decaustralia named in 2 posts, 8 August 2026 – 9 August 2026
@deevies11 named in 2 posts, 8 August 2026 – 9 August 2026
@jasonoli12 named in 2 posts, 8 August 2026 – 9 August 2026
@rex_fos named in 2 posts, 8 August 2026 – 9 August 2026
@sampathsudarma named in 2 posts, 8 August 2026 – 9 August 2026
@xavio_ai named in 2 posts, 8 August 2026 – 9 August 2026
@yusur1246 named in 2 posts, 8 August 2026 – 9 August 2026
@zzqwaa612 named in 2 posts, 8 August 2026 – 9 August 2026
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 25 September 2026 — this
entry's latest reading, not the date you are reading this.
“BETHEL Blockchain Platform Announcement” (@bethelplatform), 4,222 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/bethelplatform.
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.