
Channel
FightCity π
@fightcity5
On this record: Growth Β· Engagement Β· Cite this entry
6,715subscribers
-173 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 | -1002032347691 |
|---|---|
| Type | Channel |
| Username | @fightcity5 |
| Created | Between 1 November 2023 and 31 May 2024 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/fightcity5 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 04:39 | 6,715 | -15 |
| 1 Sept 2026, 13:36 | 6,730 | -23 |
| 29 Aug 2026, 12:59 | 6,753 | -12 |
| 27 Aug 2026, 21:33 | 6,765 | no change |
| 26 Aug 2026, 21:33 | 6,765 | -12 |
| 24 Aug 2026, 06:34 | 6,777 | -33 |
| 20 Aug 2026, 15:46 | 6,810 | -17 |
| 17 Aug 2026, 16:08 | 6,827 | -17 |
| 14 Aug 2026, 19:06 | 6,844 | -14 |
| 11 Aug 2026, 12:32 | 6,858 | -22 |
| 8 Aug 2026, 07:01 | 6,880 | -8 |
| 7 Aug 2026, 12:44 | 6,888 | 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 5 September 2026 β this entry's latest reading, not the date you are reading this.
βFightCity πβ (@fightcity5), 6,715 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/fightcity5.
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.