Channel
@BotXCreatorDevelopers
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
18subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001530170781 |
|---|---|
| Type | Channel |
| Username | @BotXCreatorDevelopers |
| Description | ✅ Official Channel of @BotXCreatorBot for Developers 🧰 Real-Time Fix: @BotXCreatorBugFixing 📢 Updates: @BotXCreator 🌐 This channel is part of @NeleBots © Website: botx.nelebots.com |
| Created | 26 March 2022 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BotXCreatorDevelopers |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:31 | 18 | no change |
| 6 Aug 2026, 22:33 | 18 | first reading |
6 posts held, back to 26 March 2022 — 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 pageof 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 6 posts for this entry, the most recent from 1 June 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 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.
5 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 3 | 60.0% | |
| ❤ | 2 | 40.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 4 of the 6 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 5reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 26 March 2022 to 1 June 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
It's easy to setup the Bot X Framework?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🟢 First release of Bot X Framework! You can now create your own test bot to create custom plugins, with custom classes and translations! When your plugin will be released the translations will be available on our Localization Bot! Start setting up your Bot and if you need help just write in the group chat of @BotXCreatorDevelopers! 😼 Visit our GitHub page, we have also published the Management plugin as a complete…
❤🔥3❤1
🤖 Bot X Creator Test Framework From today the framework for Bot X Creator will be under development, it will be a copy of NeleBot X created specifically for testing Bot X Creator plugins, using postgresql and redis databases and data between plugins!
🇮🇹 Riserviamo i primi test per gli sviluppatori italiani! Entrando sul gruppo di questo canale potrete avere accesso agli Addons di NeleBot X che troverete sul mio GitHub, vi basterà avere un'idea sul plugin da creare e iniziare a svilupparlo sull'ambiente NeleBot X Framework già open source su GitHub! 🇬🇧 We reserve the first tests for Italian developers, but they will come for everyone!
✅ Official Bot X Creator channel for Developers Here you can see any update about Developers! 💡 What are the ideas for developers? • Custom plugins development: you can create new plugins to all of the BXC users, or to only one user! • The plugin can be developed by more than one developer! • Plugins can be deactived or actived by its developers! • You can sell the use of your plugin (not the source), obviously …
❤1
Channel created
Showing the 6 most recent of 6 posts we hold for @BotXCreatorDevelopers. 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.
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.
It's easy to setup the Bot X Framework?
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 6 most recent posts we hold, published 26 March 2022 to 1 June 2024. 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.
Citation-graph rank — 194,864 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Bot X Creator for Developers” (@BotXCreatorDevelopers), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/BotXCreatorDevelopers.
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.