Telegram RegisterThe public register of Telegram
Telegram profile photo for Crypto Baltazar

Channel

Crypto Baltazar

@cryptobaltazar

On this record: Topic · Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

5,963subscribers

-393 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-1001776733770
TypeChannel
Username@cryptobaltazar
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live17 October 2026
Measurements held19
Confirmed unchanged1 time, most recently 17 October 2026
On Telegramt.me/cryptobaltazar

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 62% 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

5,9636,3586,160.57 August 2026 — 6,356 subscribers7 August 2026 — 6,358 subscribers11 August 2026 — 6,347 subscribers14 August 2026 — 6,334 subscribers17 August 2026 — 6,325 subscribers20 August 2026 — 6,301 subscribers24 August 2026 — 6,269 subscribers27 August 2026 — 6,245 subscribers28 August 2026 — 6,245 subscribers30 August 2026 — 6,215 subscribers2 September 2026 — 6,195 subscribers7 September 2026 — 6,140 subscribers12 September 2026 — 6,120 subscribers15 September 2026 — 6,106 subscribers29 September 2026 — 6,050 subscribers6 October 2026 — 6,023 subscribers12 October 2026 — 5,990 subscribers15 October 2026 — 5,977 subscribers17 October 2026 — 5,963 subscribers7 August 202617 October 2026
19 measurements spanning 72 days, net -393. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,904–6,417 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Oct 2026, 22:365,963-14
15 Oct 2026, 08:065,977-13
12 Oct 2026, 11:305,990-33
6 Oct 2026, 03:186,023-27
29 Sept 2026, 01:366,050-56
15 Sept 2026, 18:396,106-14
12 Sept 2026, 00:596,120-20
7 Sept 2026, 12:566,140-55
2 Sept 2026, 12:056,195-20
30 Aug 2026, 22:046,215-30
28 Aug 2026, 22:316,245no change
27 Aug 2026, 15:136,245-24
24 Aug 2026, 14:576,269-32
20 Aug 2026, 15:126,301-24
17 Aug 2026, 10:336,325-9
14 Aug 2026, 00:586,334-13
11 Aug 2026, 01:176,347-11
7 Aug 2026, 20:126,358+2
7 Aug 2026, 08:126,356first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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.

Мороженое
@na_morozhenoe · 1,695,350
Telegram ranks this channel #1 of 31 here — alongside 30 others — read 31 August 2026
Futureverse ($ROOT)
@futureverse_meta · 34,195
Telegram ranks this channel #18 of 70 here — alongside 69 others — read 2 September 2026
Crypto BOOM
@booms_crypto · 20,012
Telegram ranks this channel #43 of 78 here — alongside 77 others — read 3 October 2026
Криптопатолог | Новости | Инвестиции
@criptopatolog · 78,032
Telegram ranks this channel #56 of 95 here — alongside 94 others — read 18 August 2026
CryptoNic
@CryptoNicHouse · 25,043
Telegram ranks this channel #83 of 85 here — alongside 84 others — read 17 September 2026

This channel appears in 5 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 October 2026 — this entry's latest reading, not the date you are reading this.

“Crypto Baltazar” (@cryptobaltazar), 5,963 subscribers as measured 17 October 2026. Telegram Register, tgregister.com/channel/cryptobaltazar.

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.