30 Jun 2024, 13:59 UTC≈3,820 viewsread 6 August 2026
https://x.com/s_alderoty/status/1807411683956052081?
Channel
Ripple „Rumours“
@xrpchat
On this record: Growth · Engagement · Posts · Cite this entry
897subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001122679776 |
|---|---|
| Type | Channel |
| Username | @xrpchat |
| Created | Between 1 June 2017 and 30 September 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 20 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 20 August 2026 |
| On Telegram | t.me/xrpchat |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Aug 2026, 19:45 | 897 | +1 |
| 14 Aug 2026, 19:34 | 896 | -2 |
| 6 Aug 2026, 14:17 | 898 | no change |
| 6 Aug 2026, 02:45 | 898 | first reading |
Engagement
20 posts held, back to 24 May 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 pageof 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 30 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
29 Jun 2024, 15:02 UTC≈3,990 viewsread 6 August 2026
https://x.com/ripplexrpie/status/1807005894468575725?s=46&t=
24 Jun 2024, 21:00 UTC≈4,060 viewsread 6 August 2026
https://x.com/CreamCheeseXFS/status/1805343206605046243
23 Jun 2024, 20:55 UTC≈3,750 viewsread 6 August 2026
https://bitcoinist.com/ripple-case-may-end-without-sec-appeal
23 Jun 2024, 12:19 UTC≈2,260 viewsread 6 August 2026
https://x.com/bgarlinghouse/status/1804187612326056097?s=46&t=1
21 Jun 2024, 07:29 UTC≈2,150 viewsread 6 August 2026
https://www.coindesk.com/policy/2024/06/20/california-judge-breaks-with-new-york-counterpart-sends-ripple-securities-lawsuit-to-trial/
17 Jun 2024, 16:20 UTC≈1,890 viewsread 6 August 2026
https://timestabloid.com/ripple-confirms-10-ten-cbdc-partnerships/
17 Jun 2024, 14:43 UTC≈1,260 viewsread 6 August 2026
https://x.com/edward_farina/status/1802710941752004717?s=46
17 Jun 2024, 08:21 UTC≈1,370 viewsread 6 August 2026
https://news.bitcoin.com/sec-now-demands-102-6-million-penalty-from-ripple-in-xrp-case/
15 Jun 2024, 21:17 UTC≈1,030 viewsread 6 August 2026
https://coingape.com/ripple-ceo-reveals-collaboration-with-10-governments-on-cbdcs/
15 Jun 2024, 12:32 UTC791 viewsread 6 August 2026
https://x.com/amonbuy/status/1801896848380031119?s=46
14 Jun 2024, 13:54 UTC765 viewsread 6 August 2026
https://x.com/_crypto_barbie/status/1801602745545244847
Showing the 12 most recent of 20 posts we hold for @xrpchat. 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 20 August 2026 — this entry's latest reading, not the date you are reading this.
“Ripple „Rumours“” (@xrpchat), 897 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/xrpchat.
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.