Ca : 0x4239a548c21ebd9e81b5918937e49d28381c9919 Moon or dust?

Channel
Coin Fly
@CoinFlying
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001571765837 |
|---|---|
| Type | Channel |
| Username | @CoinFlying |
| Created | Between 1 August 2021 and 22 December 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/CoinFlying |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 20:16 | 2 | no change |
| 7 Aug 2026, 08:29 | 2 | first reading |
Engagement
18 posts held, back to 22 December 2022 — 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 18 posts for this entry, the most recent from 13 January 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 19
- Videos
- 2
- Links
- 76
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.
- Video runtime
- 5s
- Average length
- 5s
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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 18 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 22 December 2022 to 13 January 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
609 Iam dev? Who dev? Idk dev 😂 Tommorow launch Ca: 0x140b95cc088126deb3de7546b39a33106bf5254b 413 and 511 success mooning
BONK MOON Buy! 🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢🟢 💵 1.23 BNB ($315.03) 🪙 255 BM 🪪 0xdf8e…568e | Txn | Track ⏫ Position +553.66% 🔘 Market Cap $12,806 📊 Chart 🗳 Buy Now 🅰️ Alpha 🟢 Trending
BONK MOON Slow moon Confirmed, bullish name, Strong Community. Let's See Ca: 0x4e017f3df0A8f9E5d02016e1301EC6F16a0af59d Tg: https://t.me/Bonkmoonbsc Dyor/NFA
798 Chinese play's 0xf3bcdb47785bde0dc591666147902da7d3556901 Dyor
Chinese Project 0xF92cF9Ef7ED5dcb0BD90F85Db0ddcAD5fb26b076 https://t.me/RabbitCn2023 Dyor/NFA
Post in Private X10+ Here X3
Gamble play 💎 UTILITY 💎 Easiest way to make a meme Android: Memix: Download the app on Google Play https://play.google.com/store/apps/details?id=com.irl.memix.android iOS: https://apps.apple.com/us/app/memix-chat-with-memes/id6443475929 Dyor/NFA
@SafeAnalyzerbot | Memix | 🟡 | Trends 🔸 BINANCE: 0x0d482a646E3BB63ba119444bc90aCF5b8c15a5bE 👨💻 Owner: 0x...3D20d9ef00ae 💧 Liquid: 43% in Pancakeswap. 👥 Holders: 42 6.0% | 2.0% | 2.0% | 2.0% | 1.8% | 1.8% | 💲 MCap: $ 1,209 BNB:$247.01 💰 Liquidity: 2.11 WBNB 🔒 LP Lock: 99.17% locked for 7 days on Mudra 🔖 Fee: Buy: 8.00% | Sell: 16.81% 📈 Max Buy: 20000000 (0.10 WBNB…
No fud, this is real Trust Me 😜
I have it. be careful with these bastards, they share eca before publishing. Add liq 1 hr ago Lol 😜😜😜 https://t.me/NewYear1996Official
Contract Address ▪️$OREO (Dex Token) 0xF28Db5d3DDaa505937CfE27eE52D91dA73B1D740
Showing the 12 most recent of 18 posts we hold for @CoinFlying. 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.
Forward network
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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@CoinFlying 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 14 August 2026 – 14 August 2026
Cite this entry
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.
“Coin Fly” (@CoinFlying), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/CoinFlying.
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.