Supergroup
Bucket Protocol
@bucketprotocol
On this record: Topic · Growth · Engagement · Cite this entry
1,070members
-22 since we began measuring on 7 August 2026
23 online right now
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001945772007 |
|---|---|
| Type | Supergroup |
| Username | @bucketprotocol |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 October 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/bucketprotocol |
Topic
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 7 October 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 7 Oct 2026, 23:17 | 1,070 | -9 |
| 7 Oct 2026, 04:53 | 1,079 | no change |
| 30 Sept 2026, 22:37 | 1,079 | -1 |
| 16 Sept 2026, 09:22 | 1,080 | -2 |
| 12 Sept 2026, 14:38 | 1,082 | -1 |
| 8 Sept 2026, 19:21 | 1,083 | -1 |
| 3 Sept 2026, 16:00 | 1,084 | +3 |
| 27 Aug 2026, 17:27 | 1,081 | +2 |
| 24 Aug 2026, 20:13 | 1,079 | -4 |
| 20 Aug 2026, 20:43 | 1,083 | +2 |
| 17 Aug 2026, 16:46 | 1,081 | -4 |
| 10 Aug 2026, 19:18 | 1,085 | -6 |
| 8 Aug 2026, 05:02 | 1,091 | -1 |
| 7 Aug 2026, 20:29 | 1,092 | 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 October 2026 — this entry's latest reading, not the date you are reading this.
“Bucket Protocol” (@bucketprotocol), 1,070 members as measured 7 October 2026. Telegram Register, tgregister.com/channel/bucketprotocol.
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.