Channel
@XMagnetic
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,875subscribers
-102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001612547979 |
|---|---|
| Type | Channel |
| Username | @XMagnetic |
| Description | Official chat: https://t.me/XMagnetic_chat DEX, AMM & Farming: https://xmagnetic.org Twitter: https://twitter.com/MagneticXRPL CEO: @X_Magnetic |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/XMagnetic |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:26 | 10,875 | -11 |
| 12 Aug 2026, 03:54 | 10,886 | -17 |
| 11 Aug 2026, 05:23 | 10,903 | -20 |
| 10 Aug 2026, 05:28 | 10,923 | -15 |
| 9 Aug 2026, 04:21 | 10,938 | -12 |
| 8 Aug 2026, 06:10 | 10,950 | -10 |
| 7 Aug 2026, 07:30 | 10,960 | -17 |
| 6 Aug 2026, 05:10 | 10,977 | no change |
| 6 Aug 2026, 04:49 | 10,977 | first reading |
20 posts held, back to 30 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof 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 19 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
456 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 36.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 165 | 36.2% | |
| 👍 | 115 | 25.2% | |
| 🔥 | 110 | 24.1% | |
| 🤬 | 18 | 3.95% | |
| 🙏 | 12 | 2.63% | |
| 🤔 | 11 | 2.41% | |
| 🦄 | 11 | 2.41% | |
| 👌 | 10 | 2.19% | |
| 🤯 | 4 | 0.877% |
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 20 of the 20 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 456reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 December 2025 to 19 June 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.
Service Status Update As you may know, Magnetic has been unavailable for the past few days. During this period, reward distribution for farming pools was also affected and did not function as intended. To compensate for the downtime, the duration of all farming pools has been extended by the exact amount of time during which the services were unavailable. All rewards will be distributed in full. We also expect to r…
❤15👍6
Maintenance work on Magnetic is taking longer than expected. The delay is due to issues with the new service provider. The provider has informed us that work is still ongoing and that service restoration is expected within the next 24 hours. We also expect to regain access to the data for Memepad and Factora soon, which will allow us to restore these services as well. Thank you for your patience and understanding. …
❤10👍7👌2🤯2
Technical maintenance is currently in progress. Our physical servers are being relocated to a new data center. The estimated service downtime is approximately 6-12 hours. We apologize for any inconvenience and appreciate your patience.
👍11🤬8🙏2
Magnetic has been restored and is now operating normally. The only service that remains unavailable is Memepad. As soon as we regain access to the data, the service will be brought back online. If your project's token has lost its icon or any associated information, please contact @X_Magnetic and resend the relevant details so that we can update the token information. We sincerely apologize for any inconvenience c…
❤14🦄1
Issues accessing xmagnetic.org The provider we migrated to yesterday has also experienced an outage. We are actively working on the situation and evaluating next steps. As a result, xmagnetic.org will be temporarily unavailable. We are making every effort to restore service as quickly as possible. The new provider we migrated to is currently experiencing issues. The Finland region has been unavailable since yesterd…
🙏9👍4❤3🤯1
Magnetic has been restored and is now operational. Most services are available. However, part of the website is still not functioning. Unfortunately, we were unable to retrieve all data from the affected servers (we are hoping for their recovery soon). The issue was caused by the shutdown of the hosting provider vdsina.com. We still do not have access to our servers, and the provider is referring to third-party iss…
🔥14👍7❤4🤬1🙏1
We are currently experiencing serious accessibility issues with xmagnetic.org. Our hosting provider has been experiencing an outage for several hours. We believe they may be under a DDoS attack and are awaiting a resolution from their team. We apologize for any inconvenience this may cause. Our servers are hosted by vdsina.com, and you can check the status of their services independently.
👍12🤔6❤5🤬3👌2
🟢Burning 4.4 $MAG from Dice and Crash 1% of each dice game goes to buy back and burn MAG! Today we burned another 4.4 MAG Transaction Dice | Crash
🔥10❤4👍3
🟢Major NFT Update on Magnetic 1️⃣ The NFT marketplace page has been revamped: ✔️ Added “Trending collections” and “Recent sales” sections (you can now view recent sales across all marketplaces) 2️⃣ The individual NFT page now includes more detailed information on orders, transaction history, and NFT metadata 3️⃣ The NFT collection page interface has been redesigned Broker fee on Magnetic = 0% 🔥 (On all other popu…
🔥11👍9❤7🦄1
🟢Burning $MAG worth 3600$ from Dice and Crash 1% of each dice game goes to buy back and burn MAG! Today we burned another 3.66 MAG (~3,600$) Transaction Dice | Crash
🔥10❤4🦄4
There were technical issues on Magnetic over the past few hours. All issues have now been resolved, and the website is operating normally. На Magnetic были некоторые технические неполадки последние несколько часов. Сейчас все ошибки устранены и сайт работает в штатном режиме.
❤16👌5👍4
🟢 30-day statistics for dApps on XRPL Magnetic is leading by a wide margin: Volume — over 5.4 million XRP More than 5,600 unique users who signed at least one transaction XRPL Radar
🔥8👍6🦄3❤1🤔1
Showing the 12 most recent of 20 posts we hold for @XMagnetic. 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 — 145,218 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 3 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“XMagnetic Official” (@XMagnetic), 10,875 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/XMagnetic.
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.