Telegram RegisterThe public register of Telegram

Channel

Phoenix Revive: Announcements

@PhoenixReviveNews

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

18subscribers

+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-1001780704086
TypeChannel
Username@PhoenixReviveNews
DescriptionA token that can automatically relaunch itself. http://phoenixrevive.io http://t.me/PhoenixRevive https://www.reddit.com/r/PhoenixRevive https://discord.gg/WKQNpKPjBf
CreatedBetween 1 December 2021 and 17 October 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/PhoenixReviveNews

Growth

187 August 2026 — 18 subscribers11 August 2026 — 18 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 17–19 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 19:0118no change
7 Aug 2026, 08:2118first reading

Engagement

20 posts held, back to 17 October 2022the 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 13 April 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1
Videos
1
Links
17

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.

Video runtime
11s
Average length
11s

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

259 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 47.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12247.1%
3613.9%
❤‍🔥2810.8%
👍2710.4%
155.79%
🍾103.86%
🎉72.70%
🏆41.54%
👏31.16%
🙏31.16%
🍓10.386%
👌10.386%
🕊10.386%
😁10.386%

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 259reactions 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 17 October 2022 to 13 April 2024, 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

13 Apr 2024, 13:27 UTC210 views8 reactionsread 11 August 2026

Project Update: Status Report: The coding of our MEV bot utility has progressed well, however there are some striking competitive issues which has limited the frontrun opportunities (if any), the main one being the availability at which our MEV bot performs the transactions compared to other bots on the market which have direct access to the validator nodes. Hindsight is always 20/20, and looking back we may have b

❤‍🔥4🙏3😁1

Signed shirou | @PhoenixRevive | Developer

24 Mar 2024, 03:49 UTC221 views6 reactionsread 11 August 2026

Due to a restructure of how we operate in the future, we will not be accepting any more whale holders to the exclusive whale group at this point. You are still welcome to buy as much PXR as you want though. The restructure will be announced in early April.

🎉3👍2👌1

Signed shirou | @PhoenixRevive | Developer

31 Dec 2023, 13:02 UTC326 views16 reactionsread 11 August 2026

Happy new Year from Australia!! 🎊 🎉 Would like to thank and appreciate everyone for their continued support, I was hoping to deliver some good news before the year ends, but I will be working hard in the next few days to make the fresh new year a good start for all Phoenix Revive holders. Wishing everyone a safe and fun lasting New Years day and a fulfilling life for years to come. 🙏

❤‍🔥84🎉4

Signed shirou | @PhoenixRevive | Developer

11 Dec 2023, 07:07 UTC336 views20 reactionsread 11 August 2026

Dear Valued Investors, We are writing to you today with an update regarding a recent incident involving a frontrunning attack (ironically not us). Unfortunately, one of our newest investor (22.5 BNB) fell victim to this attack (and lost around 28k tokens), and we deeply regret the losses incurred. We want to assure you that we take these matters very seriously. We have already implemented smart contract-level prote

96👍3🔥2

6 Dec 2023, 23:08 UTC279 views20 reactionsread 11 August 2026

Dear Investors, After six months of intense research and development, I'm thrilled to share that our hard work is bearing fruit. We've cracked the code on three major breakthroughs in our arbitrage techniques, overcoming the hurdles of competition and gas optimization. These breakthroughs, which remain confidential for your benefit and ours, will significantly enhance our ability to identify and capitalize on profi

🔥191

1 Nov 2023, 22:07 UTC314 views9 reactionsread 11 August 2026

Thank you, everyone, for your patience as we have been working tirelessly in the background, clearing many hurdles in the process. Firstly, I want to apologise for the lack of presence and availability in the past few months. There were several reasons for my missing in action, but the main ones were just trying to get sh*t done. It might have been a bit selfish and cowardly for such a radical approach. Still, it ga

8👍1

12 Jun 2023, 22:52 UTC365 views20 reactionsread 11 August 2026

Here are some updates and I'm going to try cover everything and be transparent as possible with the current situation. - Currently the problem we were facing is there are too many competition on Ethereum, and gas prices are too high and we cannot compete with low budget. - I've been doing lots of experiments back on BSC using the knowledge we gained, and looks like it's alot more feasible than before. - Finally work

🔥15👍211❤‍🔥1

9 May 2023, 19:35 UTC416 views10 reactionsread 11 August 2026

While we are working on a feasible solution for the frontrun this weekend, we've just upgraded our tracker / parent contract for a quick win on this item https://phoenixrevive.canny.io/main/p/swap-and-liquify-threshold Since there has been some nice bullish price action in the past few weeks. The $PXR tokens are now worth 10x more than it did before and the liquify function from the contract is selling more than it

71🍓1🔥1

5 Apr 2023, 23:17 UTC454 views15 reactionsread 11 August 2026

FrontRun Announcement In the past few weeks, I have been through countless iterations of changes and optimizations of the frontrun ecosystem. The results have not been what we have hoped for dispite our best effort. We had a long internal discussion with the team and have decided to launch the FrontRun bot on Ethereum instead. 1. Ethereum has a much higher volume and will produce better results. 2. Ethereum tran

🔥123

28 Jan 2023, 20:38 UTC383 views15 reactionsread 11 August 2026

I have created a customer feedback board on canny https://phoenixrevive.canny.io/ what this will allow is to track upcoming features and utilities that are in the works, you can see it's progress and sharing insights to the public. Since the board is public, everyone is welcome to submit suggestions and feedbacks, with most voted items will be under review and once we determine it's value, impact and effort it will b

🔥113👍1

9 Jan 2023, 21:19 UTC290 views9 reactionsread 11 August 2026

Hello everyone, I hope you all had a good long break over the festive season. Happy new year! 🎉 Thank you to everyone who is still here and believes in the project. We are back in full gear and ready to get this project rolling. First, I wanted to announce how we will handle migrations and revives. An observation is that if it gets done without much hype, it gets a different vibe than a real launch. And so, moving

👏3🔥3❤‍🔥21

6 Nov 2022, 20:34 UTC259 views3 reactionsread 11 August 2026

We are now live on Nomics https://twitter.com/NomicsUpdates/status/1589336619777228800 Smash those buttons! 🔥 Like => Retweet => Comment Listing page: https://nomics.com/assets/pxr-phoenix-revive

🔥3

Showing the 12 most recent of 20 posts we hold for @PhoenixReviveNews. 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

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Phoenix Revive: Announcements” (@PhoenixReviveNews), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/PhoenixReviveNews.

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.