Channel
TapWallet News
@TapWalletNews
On this record: Growth · Engagement · Cite this entry
7,277subscribers
-92 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 | -1001942576552 |
|---|---|
| Type | Channel |
| Username | @TapWalletNews |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/TapWalletNews |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 00:45 | 7,277 | -16 |
| 26 Aug 2026, 21:22 | 7,293 | no change |
| 25 Aug 2026, 00:18 | 7,293 | -29 |
| 21 Aug 2026, 02:26 | 7,322 | -19 |
| 17 Aug 2026, 20:14 | 7,341 | -2 |
| 14 Aug 2026, 18:13 | 7,343 | -16 |
| 11 Aug 2026, 18:12 | 7,359 | +2 |
| 8 Aug 2026, 07:54 | 7,357 | -12 |
| 7 Aug 2026, 13:10 | 7,369 | 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“TapWallet News” (@TapWalletNews), 7,277 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/TapWalletNews.
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.