Telegram RegisterThe public register of Telegram
Telegram profile photo for Swift OTC

Channel

Swift OTC

@swiftotc_announcements

On this record: Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

3,586subscribers

-82 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001994183723
TypeChannel
Username@swiftotc_announcements
Created29 January 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/swiftotc_announcements

Growth

3,5863,6683,6277 August 2026 — 3,668 subscribers7 August 2026 — 3,668 subscribers11 August 2026 — 3,657 subscribers14 August 2026 — 3,647 subscribers17 August 2026 — 3,636 subscribers21 August 2026 — 3,627 subscribers24 August 2026 — 3,615 subscribers27 August 2026 — 3,611 subscribers30 August 2026 — 3,605 subscribers2 September 2026 — 3,594 subscribers7 September 2026 — 3,586 subscribers7 August 20267 September 2026
11 measurements spanning 31 days, net -82. 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 3,574–3,680 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 04:383,586-8
2 Sept 2026, 08:083,594-11
30 Aug 2026, 07:363,605-6
27 Aug 2026, 17:023,611-4
24 Aug 2026, 21:183,615-12
21 Aug 2026, 02:243,627-9
17 Aug 2026, 18:373,636-11
14 Aug 2026, 21:163,647-10
11 Aug 2026, 04:263,657-11
7 Aug 2026, 12:333,668no change
7 Aug 2026, 12:193,668first reading

Engagement

14 posts held, back to 29 January 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 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 14 posts for this entry, the most recent from 9 March 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1,332 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 49.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥66049.5%
47535.7%
👍997.43%
👏564.20%
🐳221.65%
🥰151.13%
👎50.375%

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 9 of the 14 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 1,332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 29 January 2024 to 9 March 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

9 Mar 2024, 10:06 UTC≈2,120 views5 reactionsread 7 August 2026

https://x.com/CertiKCommunity/status/1766212545990299908

👍41

8 Mar 2024, 15:52 UTC≈1,830 viewsread 7 August 2026
Photo

🔒 SwiftOTC has proudly passed the CertiK Security Assessment! We're all about elevating your trading experience with top-tier security. Gear up for the revamped platform - it's sleeker, faster, and more secure than ever! 🌐 In the meantime, get a sneak peek at our commitment to excellence. Dive into our audit and code on GitHub: https://github.com/SwiftOTC/contracts/blob/main/SwiftOTC-Certik.pdf 🧐

29 Feb 2024, 14:41 UTC≈2,210 views1 reactionsread 7 August 2026

We have introduced multi-signature authentication and implemented 48-hour time-lock controls for privileged functions in order to uphold transparency in SwiftOTC. 🛡 If you would like to learn more about how we handled the situation, read below: 📖 https://medium.com/@swiftotc/the-majority-of-smart-contracts-contain-special-functions-that-are-exclusively-accessible-to-the-0f18d85670a1

1

28 Feb 2024, 19:34 UTC≈1,740 viewsread 7 August 2026
Photo

🚀 Big updates on the way! ✨ While security audits are ongoing, we've completely revamped the UI/UX of SwiftOTC. 💫 Get ready for a sleek new look and improved user experience! 👀 Stay tuned for updates.

19 Feb 2024, 14:40 UTC≈2,410 views10 reactionsread 7 August 2026

🚀 We're thrilled to announce that CertiK is officially kicking off our security audits. We're partnering with the best to ensure unparalleled security for our users.🔒 Stay tuned for updates to see what we're brewing! 🧙‍♀️ Read more below 👇 https://medium.com/@swiftotc/swiftotc-first-audit-by-certik-2fd7cd8e30be

9👍1

13 Feb 2024, 12:49 UTC≈3,050 views61 reactionsread 7 August 2026
Photo

🔐 Exciting News, We're leveling up! Our Smart Contracts are gearing up for a top-tier security audit. ✨ Your trust is our treasure, and we're committed to ensuring unparalleled security for our users. 🛡 Stay tuned for updates and get ready for a safer, stronger trading scene! 🌟

36🔥25

8 Feb 2024, 13:36 UTC≈5,480 views97 reactionsread 7 August 2026
Photo

🎉 Big news! The SwiftOTC GitHub is now live! Soon, you'll be able to explore all our contracts & source code. Stay tuned for a transparent future with us! 🔍✨ 🔗 https://github.com/orgs/SwiftOTC/

84👍13

6 Feb 2024, 21:31 UTC≈7,750 views209 reactionsread 7 August 2026
Photo

🚀 You can now discuss with other users about the SwiftOTC Platform on our Telegram Group. ☑️ Simplify Your Trading: A user-friendly platform that transforms the complexity of crypto trades into a seamless experience. https://t.me/swiftotc_discussions

193👍12👏4

5 Feb 2024, 11:22 UTC≈7,860 views47 reactionsread 7 August 2026
Photo

SwiftOTC is here to support you at every need! ✅ Although the SwiftOTC Platform is automatic and we do not hold any of your funds, the sale being completed once a buyer is found for your offer, if you require any assistance or experience any technical difficulties you can reach us at: [email protected] t.me/swiftotc_official Thank you. 🎉

🔥43👏4

3 Feb 2024, 12:10 UTC≈13,700 views885 reactionsread 7 August 2026
Photo

💵Airdrop is live!!! 🏮Welcome to SwiftOTC Community -------------------------------------------------------------------------------------------- Participate in our Airdrop and earn 2 USDT for doing tasks. Join our airdrop bot here: @SwiftOTCAirdropbot SwiftOTC shields DeFi traders from unpredictable market turbulence, ensuring a user-friendly peer-to-peer trading experience. Airdrop rewards will be distributed

🔥592138👍67👏48🐳22🥰13👎5

Showing the 12 most recent of 14 posts we hold for @swiftotc_announcements. 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“Swift OTC” (@swiftotc_announcements), 3,586 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/swiftotc_announcements.

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.