Telegram RegisterThe public register of Telegram
Telegram profile photo for Userbot by @BulzoDev

Channel

Userbot by @BulzoDev

@BulzoDev

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Polls · Handles named that no longer answer · Cite this entry

209subscribers

-27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002850226423
TypeChannel
Username@BulzoDev
Created8 June 2025 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held7
Confirmed unchanged2 times, most recently 7 October 2026
On Telegramt.me/BulzoDev

Topic

Technology — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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

209236222.57 August 2026 — 236 subscribers8 August 2026 — 236 subscribers15 August 2026 — 224 subscribers21 August 2026 — 218 subscribers28 August 2026 — 217 subscribers6 September 2026 — 210 subscribers25 September 2026 — 209 subscribers7 August 202625 September 2026
7 measurements spanning 49 days, net -27. 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 205–240 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 13:57209-1
6 Sept 2026, 10:58210-7
28 Aug 2026, 11:38217-1
21 Aug 2026, 06:57218-6
15 Aug 2026, 00:26224-12
8 Aug 2026, 10:01236no change
7 Aug 2026, 17:08236first reading

Engagement

13 posts held, back to 8 June 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 13 September 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

445 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 37.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍16637.3%
🔥10623.8%
🎉9320.9%
❤7116.0%
😁51.12%
👏40.899%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 12 of the 13 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 445 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 8 June 2025 to 13 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
1
of 12 we hold a reading for · 8%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @BulzoDev. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 13 most recent posts we hold for this entry, published 8 June 2025 to 13 September 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

13 Sept 2025, 08:14 UTC261 views15 reactionsread 8 August 2026

▶️ DOWNTIME IN ARRIVO ▶️ Per i Beta Tester, i server saranno temporaneamente sospesi per consentire allo sviluppatore di effettuare manutenzione, introdurre nuovi moduli e verificare la stabilità di quelli già attivi. ⚙️ Aggiornamenti e sicurezza Stiamo aggiornando diversi moduli che hanno bug significativi tra cui .image e .gpinfo . Inoltre stiamo potenziando la sicurezza di .broadcast che verrà disattivato fino a …

👍9🎉6

11 Sept 2025, 06:46 UTC227 views10 reactionsread 8 August 2026

⚠️ NUOVO ACCOUNT SUPPORTO ⚠️ Purtroppo il nostro account di supporto è stato bloccato a causa dei report di alcuni utenti. Il nostro nuovo account di supporto è @Userbot_Supporto. Grazie a tutti 👍

❤3👍3🔥3🎉1

9 Sept 2025, 07:55 UTC262 views18 reactionsread 8 August 2026

🔤🔤🔤🔤🔤🔤🔤🔤 🎉 Nuovo comando aggiunto! 🎉 Come promesso, da oggi sarà disponibile per tutti i Beta Tester il nuovo comando .command ! ❓ Utilizzo ❓ Consente di creare e gestire comandi personalizzati rispondendo a un messaggio, che diventa la risposta del comando. • .command add <comando> — Aggiunge un nuovo comando. • .command del <comando> — Elimina un comando esistente. • .command list — Mostra tutti i comandi.…

❤7🎉4👍3🔥3😁1

8 Sept 2025, 20:23 UTC553 views145 reactionsread 8 August 2026
Poll

Vota il nuovo comando:

  1. .command40%
  2. .tagall13%
  3. .purge31%
  4. .ip13%
  5. .dmex3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

👍63🔥50🎉23❤9

8 Sept 2025, 20:19 UTC278 views33 reactionsread 8 August 2026

🔤🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤❓ Grazie a tutti i nostri Beta Testers per i numerosi feedback che ci state dando! 👍 Per questo vorremmo aggiungere un nuovo modulo disponibile per la Beta Testing e lasceremo decidere a voi con un sondaggio qui sotto il prossimo modulo da rilasciare! 🚀 ❓ Per conoscere il funzionamento dei comandi, apri questa pagina ❓ ⬇️ Vota il nuovo modulo qui sotto! ⬇️

🎉11🔥10👍7❤4👏1

8 Sept 2025, 10:20 UTC268 views39 reactionsread 8 August 2026

🔤🔤🔤🔤🔤🔤 🔤🔤❗️ 🔄 Aggiornamento sul trasferimento Da ieri sera fino a pochi minuti fa i nostri bot sono stati offline per consentire il trasferimento al nuovo datacenter. Gli userbot resteranno ancora attivi per alcune ore sul vecchio server, ma entro la giornata completeremo la migrazione dell’infrastruttura sul nuovo ambiente, così da garantire prestazioni migliori e tempi di risposta più rapidi, in linea con la cre…

🎉13👍9🔥9❤7😁1

7 Sept 2025, 19:02 UTC283 views14 reactionsread 8 August 2026

grazie ragazzi questo bot funziona e come avere chat gpt nel tuo cervello che anche se sei pigro risponde alle chat puoi usare comandi come se avessi il telegram premium siete davvero dei genii bravi non fermatevi mai @insazio

👍5❤3🎉3🔥2👏1

7 Sept 2025, 18:09 UTC224 views16 reactionsread 8 August 2026

Grazie mille bro il bot è fantastico. Appena ti mando anche a un mio amico che lo cercava da un botto. Se puoi potete aggiungere altri comandi con l'Intelligenza artificiale? Quelli non li hanno gli altri userbot e spaccano.

👍6❤4🔥4🎉1👏1

7 Sept 2025, 15:23 UTC344 views12 reactionsread 8 August 2026

userbot funzionante al 100%, aspetterò gli aggiornamenti futuri, veramente top 💯🔝

❤3🎉3👍3🔥2😁1

7 Sept 2025, 11:07 UTC295 views32 reactionsread 8 August 2026

🎉 INIZIANO AD ARRIVARE I PRIMI FEEDBACK!! 🎉 Grazie mille a tutti i Beta testers per il supporto ❤ Per chi volesse ricevere l'Userbot gratuito, contatti @userbot_bulzo_supporto ⬇️ A breve lascereo alcuni altri beedback ⬇️

❤10👍9🎉8🔥4👏1

2 Sept 2025, 11:26 UTC421 views72 reactionsread 8 August 2026

🔤🔤🔤🔤 🔤🔤🔤🔤🔤🔤🔤 ⚙️ | BETA TESTING APERTA ORA! La Beta dell'UserBot by @BulzoDev è ora aperta a tutti! Per chi fosse interessato a testare l'UserBot, la Beta sarà aperta a tutti gratuitamente! ❓ Entrare nella Beta Per entrare nella Beta scrivete al Supporto dove verrete guidati per fornire le informazioni necessarie per attivare il piano Beta. Il supporto risponderà immediatamente inserendovi nella beta dell'UserBot.…

👍32❤19🎉13🔥7😁1

10 Jun 2025, 15:10 UTC513 views39 reactions5 Starsread 8 August 2026
Photo

🚀 | IN ARRIVO: USERBOT BY @BulzoDev Dopo 5 mesi di sviluppo del prodotto, siamo felici di annunciare che il nostro UserBot sta per essere rilasciato! ❓ Cos'è un UserBot Per chi non conosce ancora questo tipo di bot, un UserBot è uno strumento che, integrandosi direttamente con il proprio account Telegram, consente di automatizzare molte azioni normalmente svolte manualmente dall’utente. 😊 Il Prodotto Senza esageraz…

👍17🔥12🎉7❤2😁1

Showing the 12 most recent of 13 posts we hold for @BulzoDev. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

8 Sept 2025, 20:23 UTCFinal Results219 voters

Vota il nuovo comando:

  1. .command40%
  2. .tagall13%
  3. .purge31%
  4. .ip13%
  5. .dmex3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 13 most recent posts we hold, published 8 June 2025 to 13 September 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Userbot by @BulzoDev” (@BulzoDev), 209 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/BulzoDev.

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.