
Channel
Breezwell
@breezwell_official
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,656subscribers
-60 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001331902067 |
|---|---|
| Type | Channel |
| Username | @breezwell_official |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/breezwell_official |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 09:44 | 3,656 | -6 |
| 2 Nov 2026, 23:12 | 3,662 | -2 |
| 30 Oct 2026, 14:30 | 3,664 | -9 |
| 27 Oct 2026, 13:07 | 3,673 | -3 |
| 24 Oct 2026, 07:10 | 3,676 | -3 |
| 21 Oct 2026, 08:34 | 3,679 | -4 |
| 17 Oct 2026, 20:11 | 3,683 | -9 |
| 14 Oct 2026, 13:36 | 3,692 | -6 |
| 11 Oct 2026, 06:41 | 3,698 | -8 |
| 5 Oct 2026, 00:40 | 3,706 | +2 |
| 25 Sept 2026, 22:21 | 3,704 | -4 |
| 17 Sept 2026, 02:59 | 3,708 | +1 |
| 12 Sept 2026, 22:37 | 3,707 | +2 |
| 8 Sept 2026, 21:55 | 3,705 | -7 |
| 6 Sept 2026, 23:38 | 3,712 | no change |
| 3 Sept 2026, 10:44 | 3,712 | -1 |
| 31 Aug 2026, 15:34 | 3,713 | -3 |
| 27 Aug 2026, 12:15 | 3,716 | 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@djtabremixofficial · 45,458
Telegram ranks this channel #28 of 81 here — alongside 80 others — read 27 August 2026
@alexshikdj · 54,715
Telegram ranks this channel #46 of 89 here — alongside 88 others — read 27 August 2026
@Dj_Zuxa_Music · 31,970
Telegram ranks this channel #49 of 83 here — alongside 82 others — read 5 September 2026
@djmikisofficial · 21,410
Telegram ranks this channel #82 of 90 here — alongside 89 others — read 25 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Breezwell” (@breezwell_official), 3,656 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/breezwell_official.
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.