Channel
MASTON
@maston01
On this record: Growth · Engagement · Cite this entry
3,624subscribers
-62 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 | -1002488854689 |
|---|---|
| Type | Channel |
| Username | @maston01 |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/maston01 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 01:40 | 3,624 | +10 |
| 7 Sept 2026, 19:49 | 3,614 | no change |
| 4 Sept 2026, 15:40 | 3,614 | -20 |
| 31 Aug 2026, 16:44 | 3,634 | +5 |
| 28 Aug 2026, 06:54 | 3,629 | -9 |
| 25 Aug 2026, 00:18 | 3,638 | -25 |
| 21 Aug 2026, 20:34 | 3,663 | -10 |
| 18 Aug 2026, 06:52 | 3,673 | -22 |
| 14 Aug 2026, 23:38 | 3,695 | +17 |
| 11 Aug 2026, 07:06 | 3,678 | -7 |
| 8 Aug 2026, 00:57 | 3,685 | -1 |
| 7 Aug 2026, 18:07 | 3,686 | 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“MASTON” (@maston01), 3,624 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/maston01.
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.