Channel
Swiftput official community
@SWIFTPUTCOMMUNITY
On this record: Topic · Growth · Engagement · Cite this entry
2,258subscribers
-122 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001675709202 |
|---|---|
| Type | Channel |
| Username | @SWIFTPUTCOMMUNITY |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/SWIFTPUTCOMMUNITY |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 06:20 | 2,258 | -8 |
| 4 Oct 2026, 18:41 | 2,266 | -15 |
| 25 Sept 2026, 04:20 | 2,281 | -9 |
| 17 Sept 2026, 22:24 | 2,290 | no change |
| 15 Sept 2026, 00:22 | 2,290 | -25 |
| 11 Sept 2026, 18:55 | 2,315 | -9 |
| 7 Sept 2026, 05:37 | 2,324 | -6 |
| 2 Sept 2026, 14:46 | 2,330 | -7 |
| 30 Aug 2026, 10:33 | 2,337 | -5 |
| 27 Aug 2026, 04:22 | 2,342 | -5 |
| 24 Aug 2026, 08:35 | 2,347 | -4 |
| 21 Aug 2026, 01:25 | 2,351 | -12 |
| 17 Aug 2026, 21:22 | 2,363 | -6 |
| 14 Aug 2026, 17:56 | 2,369 | -6 |
| 11 Aug 2026, 17:42 | 2,375 | -4 |
| 8 Aug 2026, 13:18 | 2,379 | -1 |
| 7 Aug 2026, 16:31 | 2,380 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Swiftput official community” (@SWIFTPUTCOMMUNITY), 2,258 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/SWIFTPUTCOMMUNITY.
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.