Supergroup
Chime Brokerage
@ChimeBrokerage
On this record: Growth · Engagement · Cite this entry
785members
-14 since we began measuring on 7 August 2026
201 online right now
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002694922394 |
|---|---|
| Type | Supergroup |
| Username | @ChimeBrokerage |
| Description | Den - @DenDispatch20 Sam - @samdustindispatcher |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 October 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 9 |
| On Telegram | t.me/ChimeBrokerage |
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 10 Oct 2026, 03:31 | 785 | no change |
| 4 Oct 2026, 05:21 | 785 | -4 |
| 18 Sept 2026, 16:36 | 789 | -3 |
| 10 Sept 2026, 22:19 | 792 | -3 |
| 1 Sept 2026, 00:56 | 795 | -4 |
| 24 Aug 2026, 07:55 | 799 | -3 |
| 15 Aug 2026, 18:58 | 802 | +2 |
| 8 Aug 2026, 16:31 | 800 | +1 |
| 7 Aug 2026, 18:06 | 799 | 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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“Chime Brokerage” (@ChimeBrokerage), 785 members as measured 10 October 2026. Telegram Register, tgregister.com/channel/ChimeBrokerage.
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.