Channel
@murphympy
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Cite this entry
81subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001581288020 |
|---|---|
| Type | Channel |
| Username | @murphympy |
| Description | #Murphy #mpy is fully Decentralized crypto which will make you financially independent with timely and small investment due to its strong road map which consists demand and supply, utilization and circulation. |
| Created | Between 1 August 2021 and 15 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/murphympy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 03:30 | 81 | no change |
| 11 Aug 2026, 03:16 | 81 | first reading |
20 posts held, back to 15 December 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 8 January 2022. 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.
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.
*ATTENTION PLEASE* Hello Murphian!! (1) Great News!! We are happy to announce that MPY Token will soon be listed on another exchange - "LA-ASSET EXCHANGE" shortly. The process for the same has already been initiated. *Congratulations to All* (2) TRC20 - BEP20 CONVERSION Technical Team is executing the process to exchange TRC20 MPY to BEP20 MPY & will be completed by 15th Jan 2022, ( 12AM UTC). Duel process of ex…
Photo, posted without a caption
TXHUUzU3zarXv6sKkmKTwDLtfbsC4TNpWX
*VERY URGENT* Dear Murphian!! The process to claim New BEP-20 MPY Token against existing TRC-20 has been initiated. You need to send existing TRC-20 Tokens to us & you will get equivalent BEP-20 MPY Tokens as replacement. You are thereby requested to follow the following process to claim your BEP-20 MPY Tokens: ● Enter the following address in "Receiving Address" to Send your existing TRC-20 MPY Toekns TXHUUzU…
VinDAX Lists MURPHYCOIN (MPY) on 2022/01/04 08:00 AM UTC VinDAX will open trading for MPY/BTC, MPY/ETH, MPY/USDT trading pairs on 2022/01/04 08:00 AM UTC. Risk warning: Cryptocurrency trading is subject to high market risk. Any assets, digital or not, may be subject to large shifts in value. You should carefully assess whether Your financial standing and tolerance for risk are suitable for buying / selling of Virtu…
*Important Announcement* Dear Murphians!! Exciting Upgradation update-2 is here for you all!! As we know the Murphy Ecosystem is finally being deployed on BSC, which is calling for bottom-to-top changes for these adaptations to new system on BSC. Hence the Listing of newly formed BEP-20 MURPHY TOKEN being forced to postpone w.r.t. scheduled listing of (existing TRX-20 Token, which already has been revoked). The l…
https://youtu.be/V8LP83yyK74
Dear Murphians!! Here comes the 1st Upgrade!! Murphy Ecosystem has finally been developed on Binance Smart Chain & testing will be completed in next 3 days & deployed. We are proud & excited to announce that your project will now run on more credible POS blockchain BSC. During this upgradation period you may face inconveniences. Be updated, inform the community around & wait for our next announcement which shall…
Photo, posted without a caption
Sticker, posted without a caption
Like our Management Training ?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Are you excited with us!
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 20 posts we hold for @murphympy. 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 2 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.
Like our Management Training ?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Are you excited with us!
Shares as published. No per-option vote count is published by Telegram, so none is 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 20 most recent posts we hold, published 15 December 2021 to 8 January 2022. 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 — 785,962 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.
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.
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.
“Murphy Coin” (@murphympy), 81 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/murphympy.
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.