Channel
@mailtm
On this record: Growth · Engagement · Posts · Cite this entry
2,594subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001302938302 |
|---|---|
| Type | Channel |
| Username | @mailtm |
| Created | 6 June 2020 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/mailtm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 17:44 | 2,594 | +1 |
| 20 Aug 2026, 14:06 | 2,593 | +2 |
| 17 Aug 2026, 18:34 | 2,591 | +3 |
| 14 Aug 2026, 18:23 | 2,588 | +3 |
| 11 Aug 2026, 19:18 | 2,585 | +1 |
| 7 Aug 2026, 22:00 | 2,584 | no change |
| 7 Aug 2026, 21:57 | 2,584 | first reading |
20 posts held, back to 6 June 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 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 June 2022. An engagement rate over an empty window would be a number about nothing.
- Planned maintenance (~9 hours from now): Start: 2022-06-27 0:00 UTC+0 Estimated end: 2022-06-27 02:00 UTC+0 In the above-mentioned period, we are going to perform database maintenance. This will lead to the temporary unavailability of API as well as delivery of incoming emails will be delayed. We apologize for any inconvenience and kindly back up your email messages as always. Thanks!
- Maintenance has been completed: We are glad to inform you that maintenance has been completed. Email messages that were queued up will be coming up shortly. Thanks!
- Urgent maintenance (~3 hours from now): Start: 2022-02-01 21:00 UTC+0 Estimated end: 2022-02-02 03:00 UTC+0 In the above-mentioned period, we are going to perform database maintenance and clean up emails. This will lead to the temporary unavailability of API as well as delivery of incoming email will be delayed. Please, kindly back up your email messages. We apologize for any inconvenience. Thanks!
- Maintenance has been completed: We are glad to inform you that maintenance has been completed. Email messages that were queued up will be coming up shortly. Thanks!
- Planned maintenance (~12 hours from now): Start: 2022-01-03 18:00 UTC+0 Estimated end: 2022-01-03 20:00 UTC+0 In the above-mentioned period, we are going to perform database maintenance. This will lead to the temporary unavailability of API as well as delivery of incoming email will be delayed. We apologize for any inconvenience and please, kindly back up your email messages as always. Thanks!
- Maintenance has been completed: We are glad to inform you that maintenance has been completed. Email messages that were queued up will be coming up shortly. Thanks!
- Urgent maintenance (~1 hour from now): Start: 2021-12-20 15:10 UTC+0 Estimated end: 2021-12-20 16:10 UTC+0 In the above-mentioned period, we are going to perform database maintenance and clean up emails. This will lead to the temporary unavailability of API as well as delivery of incoming email will be delayed. Please, kindly back up your email messages as the databases didn't equally split the data and we need…
- Maintenance has been completed: We are glad to inform you that maintenance has been completed. Email messages that were queued up will be coming up shortly. Thanks!
- Urgent maintenance (~1 hour from now): Start: 2021-12-07 02:00 UTC+0 Estimated end: 2021-12-07 03:00 UTC+0 In the above-mentioned period, we are going to perform database maintenance and clean up emails. This will lead to the temporary unavailability of API as well as delivery of incoming email will be delayed. Please, kindly back up your email messages as all of them will be deleted due to a glitch that wasn't…
- Queries per second have been increased Allowed queries to our API have been changed from 24 requests per minute to 8 requests per second. As the issue has been fixed with the rate limit, we've reverted the previous decrease and enabled IPv6 back as well. Thanks!
- Queries per second has been decreased Allowed queries to our API have been changed from 8 requests per second to 24 requests per minute. These changes are aimed at people who cannot set limits correctly, causing a high load on our servers and harming other users. Thanks!
- Maintenance has been completed: We are glad to inform you that maintenance for this month has been completed. Email messages that were queued up will be coming up shortly. Thanks!
Showing the 12 most recent of 20 posts we hold for @mailtm. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Mail.tm” (@mailtm), 2,594 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/mailtm.
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.