Channel
@NeleBotX
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry
31subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001413742470 |
|---|---|
| Type | Channel |
| Username | @NeleBotX |
| Description | ✅ The new official PHP Framework for Telegram Bots created NeleB54Gold! 🌐 This channel is part of @NeleBots |
| Created | 7 February 2021 — 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/NeleBotX |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:01 | 31 | no change |
| 6 Aug 2026, 22:33 | 31 | first reading |
17 posts held, back to 7 February 2021 — 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 17 posts for this entry, the most recent from 4 October 2023. 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.
✅ Released 1.3.0 version of NeleBot X Framework! • Added a new crontab file to generate crontab jobs. • All the new Bot API 6.9 methods and variables added to classes. • If you want to support us, join our group and write us some idea! 😼 See on GitHub!
💬 Little internal change to the Framework! All the variables in the $v variable, which contains all the information of the update received (and even more), will be cut: Telegram variables are becoming many and confusing, so we need to update all this disorder, we're going to change all the methods and variable names, so as to make them easier to use and at the same time keep the framework light and fast! 👍🏻 If you h…
✅ Released 1.2.0 version of NeleBot X Framework! Added support to all Bot API 6.1 methods and variables, plus I add two new useful functions, if you find any bug, please go to our support group! 🐱 See on GitHub!
🎉 Telegram has published NeleBot X Framework on the Bot samples page! http://core.telegram.org/bots/samples 🆕 NeleBot X Framework will be updated to Bot API 6.1 soon!
✅ Released 1.1.0 version of NeleBot X Framework! Added support to all Bot API 6.0 methods and variables, if you find any bug, please go to our support group! 🐱 See on GitHub!
🔜 NeleBot X update coming soon... I will soon update the NeleBot X Framework to Telegram Bot API 6.0! I only need time to do that, I'm sorry for the delay...
✅ Released 1.0.0 version of NeleBot X Framework! First release of this update, if you find any bug, please go to the support group! 🐱 See on GitHub!
🆕 The framework will be updated soon with new functions and new variables! Bot API 5.5 has been released today, and framework updates is coming soon!
➕ Added broadcast of messages to users, groups and channels! Note: use fastcgi_finish_request to close the webhook request before timeout! If you have bad connection or too many chats, the sending will be repeated indefinitely without closing requests! ⚠️ Redis required! ✌️ Comment if you find any bug!
📨 Broadcast messages to users, groups and channels! In coming on NeleBot X
✅ Released the first version of NeleBot X Framework! This is a Beta version of NeleBot X, so if you find any error or missing things, please let me know in the support group! 💬 Try the Demo 🐱 See on GitHub!
What do you want first?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 17 posts we hold for @NeleBotX. 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 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
What do you want first?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
How you want the AntiFlood to be divided?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
How do you want the AntiFlood? (Redis Only)
Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.
How do you want NeleBot X to be used?
The shares total 111%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 17 most recent posts we hold, published 7 February 2021 to 4 October 2023. 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 — 482,283 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.
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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
“NeleBot X Framework” (@NeleBotX), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/NeleBotX.
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.