Channel
@Prelax_channel
On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry
1,014subscribers
-19 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001569582778 |
|---|---|
| Type | Channel |
| Username | @Prelax_channel |
| Created | Between 1 August 2021 and 30 November 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/Prelax_channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 21:56 | 1,014 | -5 |
| 14 Aug 2026, 00:54 | 1,019 | -5 |
| 10 Aug 2026, 11:30 | 1,024 | -8 |
| 7 Aug 2026, 15:05 | 1,032 | -1 |
| 7 Aug 2026, 01:16 | 1,033 | no change |
| 7 Aug 2026, 01:04 | 1,033 | first reading |
20 posts held, back to 30 November 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 7 September 2022. An engagement rate over an empty window would be a number about nothing.
What do you think if Prelax team will develop the blockchain of Prelax (Prelax Chain)???
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Hello Prelax Community, Sorry for not talking to the community lately. But everything has a reason, after a long time developing the project and run marketing campaigns with no good results, we are negotiating with a partner to let them take over the project. Our partner is a group with a lot of experience in marketing, and we will provide them with technical support so that they can continue to develop the project …
Because of pve's oracle mechanism, the inflation of the project has skyrocketed and we don't have enough PEAX to pay for the outstanding PEAX in PVE mechanism. Therefore, in order to reduce this inflation, we would like to announce that we will burn all PEAX that has not been withdrawn by users from PvE. Sorry but this is necessary for the project to go on!
PvE Will be Closed Dear Prelax Community, We will close PvE in 24 hours because PvE has caused terrible inflation for the project Thanks!
PEW AIRDROP We tested new system with PEW token but the testing progress failed because of a lot of issues. That’s why we have to delay the PEW Airdrop until we fix this. All features will use current PEAX as normally until we have new notification. Thanks!
SENT PEAX as Vesting Plans Source: Swap.Prelax.io - 20% after 11th January 2022 Source: PVP Game - 20% after 11th January 2022
We are still building up new mechanism of PvP anf it is not completed. That’s why we can not airdrop PEW tomorrow. Thanks!
PEW Airdrop We are building new mechanism of PvP so PEW airdrop will be delayed until we complete the new mechanism. Estimate time is 7th January 2022 Thank you and Happy New Year!!!
PvP Update New rule of PvP, Looser will not lose anything. Winner receive the reward as link https://docs.prelax.io/key-features/prelax-battle-online-pvp
We are checking withdraw problem. Please wait
PRELAX - Soul Stone Prelax - NFT was reaches 10,000 NFT, so we will close the Soul Stone Function in some hours Thanks!
We finished sent PEAX token as vesting plans to users follow: Source: Swap.Prelax.io - 10% after 11th December 2021 Source: PVP Game - 15% after 11th December 2021
Showing the 12 most recent of 20 posts we hold for @Prelax_channel. 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 3 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.
What do you think if Prelax team will develop the blockchain of Prelax (Prelax Chain)???
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Vote for airdrop PEW rule as users recommendation
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Should we remove all Bots from PvP?
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 30 November 2021 to 7 September 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 — 1,326,899 of 1,481,502entries 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.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“PRELAX | Official Channel” (@Prelax_channel), 1,014 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Prelax_channel.
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.