Channel
CorePad Official
@corepadofficial
On this record: Growth · Engagement · Cite this entry
771subscribers
-121 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 | -1001652921008 |
|---|---|
| Type | Channel |
| Username | @corepadofficial |
| Created | Between 1 December 2021 and 31 May 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 October 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/corepadofficial |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 18:38 | 771 | -5 |
| 10 Oct 2026, 04:43 | 776 | no change |
| 1 Oct 2026, 00:01 | 776 | -36 |
| 16 Sept 2026, 00:38 | 812 | -28 |
| 8 Sept 2026, 01:17 | 840 | -29 |
| 30 Aug 2026, 09:56 | 869 | -13 |
| 23 Aug 2026, 05:12 | 882 | -7 |
| 15 Aug 2026, 15:45 | 889 | -3 |
| 7 Aug 2026, 09:15 | 892 | 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 October 2026 — this entry's latest reading, not the date you are reading this.
“CorePad Official” (@corepadofficial), 771 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/corepadofficial.
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.