26 Jan 2022, 15:22 UTC≈5,170 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1486358797828251648
Channel
CryptoSword - Announcement
@SwordsCrypto
On this record: Growth · Engagement · Posts · Cite this entry
331subscribers
-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 | -1001674143499 |
|---|---|
| Type | Channel |
| Username | @SwordsCrypto |
| Created | Between 1 December 2021 and 10 January 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/SwordsCrypto |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 06:03 | 331 | -3 |
| 8 Aug 2026, 01:52 | 334 | no change |
| 7 Aug 2026, 04:17 | 334 | first reading |
Engagement
20 posts held, back to 10 January 2022 — 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 26 January 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
21 Jan 2022, 14:01 UTC≈4,680 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1484519495242633220
18 Jan 2022, 17:35 UTC≈4,930 viewsread 7 August 2026
In order to resolve the bot trading issue, the team decided to transfer the liquidity of the pool to the new contract, which will bring a better gaming experience and slippage to prevent auto trades. The transfer will take several days to finish, thank you for your understanding and support, Challengers! ⚔️⚔️
18 Jan 2022, 07:57 UTC≈3,500 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1483346898727571457
15 Jan 2022, 11:49 UTC≈3,440 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1482318729140576259
14 Jan 2022, 15:05 UTC≈3,020 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1482004968974413828
14 Jan 2022, 13:27 UTC≈2,470 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481981160636891136
13 Jan 2022, 08:35 UTC≈2,140 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481545181467869185
13 Jan 2022, 04:26 UTC≈2,130 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481482515932061696
13 Jan 2022, 03:50 UTC≈2,060 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481473578411327489
12 Jan 2022, 14:07 UTC≈2,350 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481266412832583680
12 Jan 2022, 07:52 UTC≈2,400 viewsread 7 August 2026
https://twitter.com/CryptoSwordsP2E/status/1481172143996293120
Showing the 12 most recent of 20 posts we hold for @SwordsCrypto. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“CryptoSword - Announcement” (@SwordsCrypto), 331 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/SwordsCrypto.
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.