🚀 New Release: 26.05 Enhanced SMS/MMS handling, migrated storage to MMKV, added USSD support, improved CI/CD, and introduced interactive Telegram commands.

Channel
Telegram SMS Changelog
@tg_sms_changelog_eng
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
260subscribers
+13 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 | -1001303931937 |
|---|---|
| Type | Channel |
| Username | @tg_sms_changelog_eng |
| Created | Between 1 March 2018 and 11 October 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/tg_sms_changelog_eng |
Topic
Technology — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 17 Sept 2026, 04:20 | 260 | -1 |
| 9 Sept 2026, 07:54 | 261 | +2 |
| 30 Aug 2026, 17:05 | 259 | +5 |
| 22 Aug 2026, 23:47 | 254 | +1 |
| 15 Aug 2026, 10:23 | 253 | +6 |
| 8 Aug 2026, 09:34 | 247 | no change |
| 7 Aug 2026, 23:51 | 247 | first reading |
Engagement
18 posts held, back to 11 October 2020 — 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 page 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 18 posts for this entry, the most recent from 21 May 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
New feature: you can now choose the type of messages you want to CC to other platforms
New feature: You can now CC messages to other platforms.
New feature: You can now customize message templates
Telegram SMS Changelog pinned «SMS forwarding bot that runs on your Android device. Project repository: https://github.com/telegram-sms Privacy Policy: https://telegram-sms.com/privacy-policy.html User manual: https://telegram-sms.com/ Config generation tool: https://config.telegram-sms.com/»
SMS forwarding bot that runs on your Android device. Project repository: https://github.com/telegram-sms Privacy Policy: https://telegram-sms.com/privacy-policy.html User manual: https://telegram-sms.com/ Config generation tool: https://config.telegram-sms.com/
https://www.xda-developers.com/update-xda-labs/
https://github.com/telegram-sms/telegram-sms/releases/tag/master-44d30487-202101171529
https://www.xda-developers.com/big-changes-to-xda-forums-are-coming-soon/
Because the XDA updates itself to XDA2021, XDA Labs has been closed. I am sorry for this and I can no longer provide the XDA Lab version of Telegram SMS. You can still use the GitHub version to update your Telegram SMS. If you request a refund, please contact me via [email protected]
https://github.com/telegram-sms/telegram-sms/releases/tag/master-4e14e85d-202012060102 master-4e14e85d-202012060102 - Fix retransmission errors and solve performance problems - Add cancel function for interactive SMS sending - Fix the crash caused by log cache too large - Fix the problem of repeatedly sending the charger disconnection information - Now the unprocessed messages will be ignored after the chat co…
New feature in progress: Reply confirmation
Showing the 12 most recent of 18 posts we hold for @tg_sms_changelog_eng. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Telegram SMS Changelog” (@tg_sms_changelog_eng), 260 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/tg_sms_changelog_eng.
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.