
Channel
⏤ 𝟔𝟗 ៸
@m3ikxu
On this record: Growth · Engagement · Cite this entry
7,641subscribers
+2,079 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 | -1002342144275 |
|---|---|
| Type | Channel |
| Username | @m3ikxu |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/m3ikxu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 20:20 | 7,641 | +1,425 |
| 2 Sept 2026, 03:54 | 6,216 | -55 |
| 30 Aug 2026, 12:13 | 6,271 | +152 |
| 29 Aug 2026, 11:55 | 6,119 | no change |
| 27 Aug 2026, 04:38 | 6,119 | +68 |
| 24 Aug 2026, 12:06 | 6,051 | +9 |
| 20 Aug 2026, 10:13 | 6,042 | -86 |
| 17 Aug 2026, 11:32 | 6,128 | +143 |
| 13 Aug 2026, 23:28 | 5,985 | +252 |
| 10 Aug 2026, 16:04 | 5,733 | +168 |
| 7 Aug 2026, 16:18 | 5,565 | +3 |
| 7 Aug 2026, 15:41 | 5,562 | 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“ ⏤ 𝟔𝟗 ៸” (@m3ikxu), 7,641 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/m3ikxu.
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.