
Channel
MSRC-IL/黑客漏洞SQL入侵
@liyummm
On this record: Growth · Engagement · Cite this entry
4,969subscribers
-1,023 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 | -1002495317371 |
|---|---|
| Type | Channel |
| Username | @liyummm |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/liyummm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 08:57 | 4,969 | -83 |
| 2 Sept 2026, 16:57 | 5,052 | -66 |
| 1 Sept 2026, 11:52 | 5,118 | no change |
| 30 Aug 2026, 20:25 | 5,118 | -124 |
| 27 Aug 2026, 16:27 | 5,242 | -140 |
| 24 Aug 2026, 18:54 | 5,382 | -122 |
| 20 Aug 2026, 16:43 | 5,504 | -96 |
| 17 Aug 2026, 19:15 | 5,600 | -120 |
| 15 Aug 2026, 00:55 | 5,720 | -95 |
| 11 Aug 2026, 22:47 | 5,815 | -109 |
| 8 Aug 2026, 17:37 | 5,924 | -68 |
| 7 Aug 2026, 18:54 | 5,992 | 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“MSRC-IL/黑客漏洞SQL入侵” (@liyummm), 4,969 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/liyummm.
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.