Channel
@FireXUb
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
92subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001649519743 |
|---|---|
| Type | Channel |
| Username | @FireXUb |
| Description | 🔷 Support:- @FirexSupport 🔷 OT Group:- @FirexUserbot 🔷 Channel:- @Fire_X_Channel • Powered by @TheCodeTech |
| Created | Between 1 October 2021 and 12 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/FireXUb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 13:45 | 92 | no change |
| 7 Aug 2026, 04:08 | 92 | first reading |
20 posts held, back to 12 October 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 20 posts for this entry, the most recent from 25 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 19 days, that account will self-destruct and this channel may no longer have an owner.
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 7 days, that account will self-destruct and this channel may no longer have an owner.
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
New Bot Deploy Video Part 2
Posted without readable text
New Bot Deploy Video
🔊Guys what we said yesterday that we are going to publish an amazing new repo to our renowned FIREX Userbot, is released now. 🌀Repo Link:- Click Here 🌀Chat :- @FirexSupport > Deploy now by open the new repository and inform us if you find any bugs. We will solve it soon. < ##Amazing Features ------------------------------------ • This is the telegram most safest, hack free telegram userbot. • Easy to Deploy and…
🎉Guys Today we are going to release a new repo which will be the best and bugs free userbot in telegram. For more updates kindly join @FireXUb and join to deploy @FirexSupport to stay used.
🔥Method For Deploy FireX Userbot on Heroku🔥 ➡️ First Make A GitHub Account 🔹 Go To main repo and Fork 🔹Then copy forked url 🔹url looks like https://github.com/YourGitName/Fire-X 🔹Now use below url for deploy 🔹Heroku.com/deploy?template=your forked url here 🔹eg - heroku.com/deploy?template=https://github.com/yourgitname/Fire-X 🔹heroku.com/deploy?template=
.eval from firebot import bot from var import Var import asyncio username = Var.TG_BOT_USER_NAME_BF_HER bf = "@BotFather" try: await bot.send_message(bf, "/setinline") await asyncio.sleep(1) await bot.send_message(bf, f"{username}") await asyncio.sleep(1) await bot.send_message(bf, "Search") print(f"DONE inline is setted to this bot SUCCESSFULLY {username}") except BaseException as er: print(er) Set Up Inline…
We are going to push a lot of updates in Firex. We need some Dev's who are agree in contributing freely for Firex Userbot. Basic Requirement:- Known Python Known Telethon Interested Dev's should message me on @maihindu ➖➖ @FireXUb ➖➖
Showing the 12 most recent of 20 posts we hold for @FireXUb. 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.
Citation-graph rank — 804,232 of 1,350,102entries 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.
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.
@FireXUb named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“FɪʀᴇX Usᴇʀʙᴏᴛ” (@FireXUb), 92 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/FireXUb.
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.