Telegram RegisterThe public register of Telegram
Telegram profile photo for NexoHub Dev | Oficial

Channel

NexoHub Dev | Oficial

@NexoHubDev

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

116subscribers

+0 since we began measuring on 14 November 2026

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

Register entry

Telegram ID-1003607635820
TypeChannel
Username@NexoHubDev
Description📢 Canal oficial do NexoHub Dev DL Bot! 🚀 Novidades, atualizações e melhorias do bot.
Created15 October 2026 — measured — dated from the channel’s first post
First recorded14 November 2026
Last confirmed live17 November 2026
Measurements held2
On Telegramt.me/NexoHubDev

Growth

11614 Nov 2026, 08:47 — 116 subscribers14 Nov 2026, 09:22 — 116 subscribers14 Nov 2026, 08:4714 Nov 2026, 09:22
2 measurements taken within a single day. 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 115–117 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 09:22116no change
14 Nov 2026, 08:47116first reading

Engagement

13 posts held, back to 15 October 2026 — 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.

ERR · 30 days
96.4%
avg views ÷ 116 subscribers
Avg views / post
112
9 posts measured
Reaction rate
1.32%
reactions ÷ views · ER floor
Posts in window
10
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held13 (15 October 2026 – 14 November 2026)
Views total1,006
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 09:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
1
Links
4

Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

5 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏240.0%
👍120.0%
🔥120.0%
😁120.0%

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 5 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 5 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 15 October 2026 to 14 November 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 10 posts held from the last 30 days (30.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 01:55 UTCviews —

NexoHub Dev | Oficial pinned «🚀 ULTRATEL — CONHEÇA NOSSO NOVO APLICATIVO! 📱 Uma nova experiência do Telegram para Android! Apresentamos o UltraTel, um cliente alternativo do Telegram, desenvolvido a partir de seu código-fonte aberto, com identidade visual própria e melhorias que serão…»

14 Nov 2026, 01:55 UTC303 viewsread 14 November 2026

🚀 ULTRATEL — CONHEÇA NOSSO NOVO APLICATIVO! 📱 Uma nova experiência do Telegram para Android! Apresentamos o UltraTel, um cliente alternativo do Telegram, desenvolvido a partir de seu código-fonte aberto, com identidade visual própria e melhorias que serão adicionadas ao longo do tempo. ✨ O que você encontra no UltraTel? 💬 Acesso às suas conversas, grupos e canais do Telegram. 📸 Envio de fotos, vídeos, áudios, do…

9 Nov 2026, 13:43 UTC42 views1 reactionsread 14 November 2026
Forwarded from @BotNewsVideo

Bot API 10.4 📚 Widget Revolution HTML widgets bring custom, dynamic interfaces right into message bubbles – giving bots and AI agents a new canvas for interactive tools, games and workflows. • Bots can now send native HTML widgets with dynamic layouts, custom sizing, interactive elements and more. • Widgets can send queries and receive answers, letting users interact freely with a reactive UI. • Bots can update wid…

👏1

7 Nov 2026, 19:25 UTC49 views1 reactionsread 14 November 2026
Photo

📢 Novidade no Save Vídeo DL: chegou o suporte ao LinkedIn! Agora você pode baixar 📸 fotos, 🎥 vídeos e 🖼️ álbuns de fotos de publicações públicas do LinkedIn direto no Telegram. Nos álbuns, as fotos são enviadas juntas, na ordem da publicação. 🔗 Como usar? No LinkedIn, toque em Compartilhar → Copiar link e envie o link para o bot. Links curtos lnkd.in também funcionam. 📥 Baixe aqui: @SaveVidDLBot

😁1

3 Nov 2026, 16:54 UTC91 viewsread 14 November 2026

❗ Parece que o Telegram está enfrentando alguns problemas, e como resultado, alguns bots podem estar lentos ou offline. ✅ Parece que o problema foi resolvido.

31 Oct 2026, 14:05 UTC113 viewsread 14 November 2026

🎧 Agora o Save Vid também baixa audiolivros da Audible! Para usar, envie o link do livro no privado do bot e siga as instruções para conectar sua conta Amazon/Audible. 🔐 É necessário estar com sua conta conectada, pois a Audible exige autenticação para acessar os títulos. O livro também precisa estar salvo na biblioteca dessa mesma conta. Cada pessoa conecta a própria conta. Sua senha e seu código de verificação d…

31 Oct 2026, 09:43 UTC99 views1 reactionsread 14 November 2026

🚀 Novidades no Save Vídeo DL Bot! 🎶 Agora você pode baixar PLAYLISTS E ÁLBUNS do YouTube e Spotify! Basta enviar o link ao bot para receber as faixas. Playlists comuns do YouTube também permitem baixar os vídeos. 🌍 O bot agora está disponível em 4 idiomas: 🇧🇷 Português 🇺🇸 Inglês 🇪🇸 Espanhol 🇩🇪 Alemão Use /lang para escolher seu idioma. As mensagens, botões e o menu de comandos acompanham sua escolha! 📲 Teste agor…

👏1

28 Oct 2026, 10:08 UTC114 views1 reactionsread 14 November 2026

📱 Reddit está apresentando erros no Download. Irei corrigir até o fim do dia. ✅ Corrigido.

👍1

26 Oct 2026, 16:56 UTC120 viewsread 14 November 2026

🚀 APRESENTAMOS O NOVO NEXOHUB! 🌐 É com muita satisfação que anunciamos o lançamento do nosso novo portal oficial! 🔗 https://nexohub.dev O NexoHub nasceu com um objetivo: reunir nossos projetos, bots e serviços em um só lugar, facilitando o acesso às informações e mantendo todos por dentro das novidades. ✨ O que você encontra no nosso site? 🤖 Nossos bots: conheça os projetos disponíveis, suas funcionalidades e com…

26 Oct 2026, 14:07 UTC75 viewsread 14 November 2026

❗️ Parece que o Telegram está enfrentando alguns problemas. Como resultado, alguns bots podem ficar lentos ou fora do ar. ✅ Parece que o problema foi resolvido.

19 Oct 2026, 09:04 UTC136 views1 reactionsread 14 November 2026

🚀 Estamos evoluindo cada vez mais! 👨‍💻 Estou trabalhando ativamente para ampliar a quantidade de plataformas e serviços compatíveis com o bot, oferecendo cada vez mais possibilidades de downloads, seja de vídeos, áudios, músicas, documentos ou qualquer outro tipo de arquivo. 📥 Atualmente, nosso bot já oferece suporte a diversos serviços, e estamos trabalhando diariamente para aumentar ainda mais essa lista! 🏙 Noss…

🔥1

Showing the 12 most recent of 13 posts we hold for @NexoHubDev. 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.

Forward network

Republished by

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“NexoHub Dev | Oficial” (@NexoHubDev), 116 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/NexoHubDev.

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.