Channel
@InfinitX_FAQ
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
93subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001673410616 |
|---|---|
| Type | Channel |
| Username | @InfinitX_FAQ |
| Created | Between 1 October 2021 and 14 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/InfinitX_FAQ |
Other / unclassifiable — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 18:56 | 93 | -2 |
| 18 Sept 2026, 07:39 | 95 | -1 |
| 30 Aug 2026, 13:38 | 96 | -2 |
| 9 Aug 2026, 11:18 | 98 | no change |
| 7 Aug 2026, 01:39 | 98 | first reading |
20 posts held, back to 14 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 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 20 posts for this entry, the most recent from 17 March 2023. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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 5 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. 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 9 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.
23° Does a MarketCap chart exist ? Yes, you can follow the Mcap chart of InfinitX token by following this link ☑️
$INX Support ･ Frequently Asked Questions pinned «13°💥 COMPILATION OF WHAT YOU HAVE TO UNDERSTAND 💥 Only look at the Marketcap, not the number of tokens. 👀 - If the marketcap goes UP, your money goes UP 📈 - If the marketcap goes DOWN, your money goes DOWN 📉 The only thing that matters is : at which MC…»
22° Will my tokens decrease to 0? The number 0 does not exist in this case. If you buy a 10% share and after a rebase the supply is reduced you will still own 10%... If the supply is 3000 INX and you own 10% you have 300 tokens... If, after a rebase, the supply is reduced to 3 tokens you will still own 10% and will have 0.3 tokens in your wallet. However an INX token will be worth 1000x more than before.
21° Does rebase mean burning tokens ? Each time a rebase happens the supply gets decreased and the amount of tokens you hold gets decreased but the worth of these tokens increase so even though you hold less tokens the percentage you hold of the supply never changes.
20° How to track the Mcap of InfinitX ? You can find a history of the Mcap token by following this link.
Trustwallet BEP20 XRP ☑️
19° Is the Liquidity Pool locked ? 🔒 THE LIQUIDITY IS LOCKED 🔒 ✅ You can check it on Unicrypt : https://app.unicrypt.network/amm/pancake-v2/pair/0x9Cc177d1d3708099574a56463abEf72ebB7E87e7
18° How to track your rewards on Metamask ? 1. Open Metamask, on the top select Smart Chain for the BEP-20 Binance Smart Chain. 2. On the left click on Assets or Tokens 3. At the bottom, click on "Import tokens" 4. Add the $XRP token adress : 0x1d2f0da169ceb9fc7b3144628db156f3f6c60dbe You are now able to see your rewards on your Smart Chain main tokens list 💰
17° How to track your BEP-20 $XRP rewards on Trustwallet ? 1. On Trust Wallet, click on the parameters button in the top right-hand corner 2. Search for "XRP token" in the search bar 3. Find and check XRP token BEP20 (view screenshot) You are now able to see your rewards on your main tokens list 💰
Showing the 12 most recent of 20 posts we hold for @InfinitX_FAQ. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“$INX Support ･ Frequently Asked Questions” (@InfinitX_FAQ), 93 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/InfinitX_FAQ.
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.