Channel
TP系列備用群 @pushpaipai_bot
@paid8874
On this record: Growth · Engagement · Cite this entry
5,744subscribers
-70 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 | -1002026450490 |
|---|---|
| Type | Channel |
| Username | @paid8874 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/paid8874 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 04:19 | 5,744 | -18 |
| 31 Aug 2026, 00:33 | 5,762 | -4 |
| 30 Aug 2026, 11:34 | 5,766 | no change |
| 28 Aug 2026, 00:55 | 5,766 | -7 |
| 24 Aug 2026, 18:57 | 5,773 | -13 |
| 21 Aug 2026, 01:42 | 5,786 | -9 |
| 17 Aug 2026, 18:25 | 5,795 | -8 |
| 14 Aug 2026, 14:07 | 5,803 | -8 |
| 11 Aug 2026, 01:43 | 5,811 | -4 |
| 7 Aug 2026, 15:17 | 5,815 | +1 |
| 7 Aug 2026, 12:52 | 5,814 | 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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“TP系列備用群 @pushpaipai_bot” (@paid8874), 5,744 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/paid8874.
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.