Channel
💀Bajosuelo blog💀
@bajosueloblog
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
7,177subscribers
+50 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 | -1001780049436 |
|---|---|
| Type | Channel |
| Username | @bajosueloblog |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/bajosueloblog |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:39 | 7,177 | +3 |
| 13 Sept 2026, 20:41 | 7,174 | +5 |
| 10 Sept 2026, 05:58 | 7,169 | +8 |
| 4 Sept 2026, 23:02 | 7,161 | -2 |
| 1 Sept 2026, 16:26 | 7,163 | +8 |
| 29 Aug 2026, 15:57 | 7,155 | +6 |
| 26 Aug 2026, 22:19 | 7,149 | no change |
| 26 Aug 2026, 22:17 | 7,149 | +8 |
| 23 Aug 2026, 13:14 | 7,141 | -6 |
| 19 Aug 2026, 23:42 | 7,147 | +2 |
| 16 Aug 2026, 14:56 | 7,145 | +4 |
| 13 Aug 2026, 06:26 | 7,141 | +9 |
| 10 Aug 2026, 14:51 | 7,132 | +6 |
| 7 Aug 2026, 06:16 | 7,126 | -1 |
| 7 Aug 2026, 04:09 | 7,127 | 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.
@COMICSESP · 67,379
Telegram ranks this channel #3 of 25 here — alongside 24 others — read 29 August 2026
@Comicverso · 42,806
Telegram ranks this channel #3 of 28 here — alongside 27 others — read 29 August 2026
@estrenosdecinee · 56,965
Telegram ranks this channel #6 of 22 here — alongside 21 others — read 8 September 2026
@SeriesClubHD · 23,602
Telegram ranks this channel #10 of 49 here — alongside 48 others — read 18 September 2026
@peliculas · 482,244
Telegram ranks this channel #13 of 52 here — alongside 51 others — read 24 August 2026
@theartbooks · 26,578
Telegram ranks this channel #34 of 62 here — alongside 61 others — read 12 September 2026
This channel appears in 6 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“💀Bajosuelo blog💀” (@bajosueloblog), 7,177 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/bajosueloblog.
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.