Channel
@mobtoken
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
51subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002994820725 |
|---|---|
| Type | Channel |
| Username | @mobtoken |
| Created | Between 1 August 2025 and 25 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 3 October 2026 |
| On Telegram | t.me/mobtoken |
Crypto & trading — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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 |
|---|---|---|
| 18 Sept 2026, 09:41 | 51 | +1 |
| 9 Sept 2026, 23:38 | 50 | -2 |
| 31 Aug 2026, 01:22 | 52 | +1 |
| 10 Aug 2026, 10:31 | 51 | no change |
| 9 Aug 2026, 23:00 | 51 | first reading |
20 posts held, back to 25 October 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 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 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 9 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.
27 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 40.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 40.7% | |
| 👍 | 6 | 22.2% | |
| 😢 | 5 | 18.5% | |
| 👎 | 3 | 11.1% | |
| 🏆 | 1 | 3.70% | |
| 😭 | 1 | 3.70% |
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 12 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 27 reactions 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 25 October 2025 to 29 July 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.
THE PHONE WAS RESET... ● 9:00: A repair shop detects water damage. ● 11:00: The phone is cleaned and reset. ● 14:00: It is listed as “fully functional.” Nothing changed inside, only the story did. When verified diagnostic and repair records are linked to the device’s protected identity, hidden faults become harder to erase between sales. The seller reset the phone, not the damage.
👎1😢1
Information recorded on the blockchain cannot be tampered with, and every record remains transparent, traceable, and verifiable. In the mobile industry, this means important information such as ownership history, warranty records, insurance details, and digital services can be verified with greater confidence. As a result, it becomes easier to reduce fraud, prevent data tampering, and build more trustworthy mobile s…
👎1😭1
One of the interesting products that attracted significant attention at the CES 2026 exhibition was the Loona Deskmate—a MagSafe charging stand that transforms the iPhone into an interactive AI assistant. Once the iPhone is placed on this stand, the dedicated Loona app launches automatically, turning the phone's screen into a smart assistant with a unique face and personality. This assistant is capable of managing re…
😢1
A mobile-first token deserves a secure, pocket-sized vault. Trust Wallet is one of the most dependable mobile applications to manage your digital assets, but configuring it correctly is the secret to keeping your funds secure. Never skip the essentials—especially safeguarding your backup recovery phrase! Watch this tutorial to install Trust Wallet on your device and get it optimized for your first MOB Token transacti…
😢1
Why settle for tokens with hidden reserves when you can choose 100% transparency? MOB is a next-generation cryptocurrency built to power the global smartphone and digital device market. Watch this video to see why MOB Token is the ultimate upgrade for your digital lifestyle. @MOBToken
😢2❤1
From smartphones and accessories to insurance and app store credits, MOB brings real-world utility to the blockchain. A fair launch for a smarter mobile future. @MOBToken
❤2
✅✅✅ Today, our ecosystem experienced one of its heaviest corrections to date. A wave of large-scale sell-offs by several major holders—executed simultaneously across multiple tokens—temporarily placed significant pressure on prices. But here’s the key reality: Contrary to initial impressions, this is not a sign of weakness. It is a natural phase in the cleansing and maturation of a healthy market. From day one, o…
✅✅ Today, the market experienced a correction driven by heavy selling from some whales. However, this is not a sign of weakness it is a natural part of a healthy market's maturation. Our structure, token burning, liquidity locking, and the absence of centralized control has guided the market into a phase of base formation and more equitable distribution. Real growth, independent of whales, continues. @MOBToken
👎1
✅ Market Correction Update! We've implemented fundamental changes to shift power from whales to the community. The results will soon speak for themselves. Stay tuned. @MobToken
Not all assets are meant to move with the market. Some are built to stay steady through it. RZUSD - stability, exactly where you need it. @RZUSD_Channel
The numbers have aligned! MOB just hit a legendary $1.111 ATH. A perfect milestone! Where are we heading next? @MobToken
For a good future, you must invest TODAY! Z Generation Coin (ZGC). Launching Feb 23rd, 8 PM CET
Showing the 12 most recent of 20 posts we hold for @mobtoken. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“MOB Token” (@mobtoken), 51 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mobtoken.
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.