
Channel
Rui的小小空间
@rui_personal
On this record: Growth · Engagement · Cite this entry
4,159subscribers
+19 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 | -1002460937118 |
|---|---|
| Type | Channel |
| Username | @rui_personal |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/rui_personal |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 13:41 | 4,159 | +10 |
| 4 Sept 2026, 22:51 | 4,149 | no change |
| 2 Sept 2026, 04:07 | 4,149 | -2 |
| 30 Aug 2026, 03:14 | 4,151 | -2 |
| 26 Aug 2026, 18:08 | 4,153 | -7 |
| 23 Aug 2026, 13:07 | 4,160 | +2 |
| 20 Aug 2026, 09:54 | 4,158 | +2 |
| 17 Aug 2026, 12:13 | 4,156 | +17 |
| 14 Aug 2026, 12:16 | 4,139 | -4 |
| 11 Aug 2026, 05:12 | 4,143 | +3 |
| 7 Aug 2026, 15:06 | 4,140 | 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.
“Rui的小小空间” (@rui_personal), 4,159 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/rui_personal.
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.