Channel
@SaltSwapAnn
On this record: Growth · Engagement · Posts · Polls · Cite this entry
107subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001222122643 |
|---|---|
| Type | Channel |
| Username | @SaltSwapAnn |
| Created | Between 1 March 2018 and 29 April 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 4 September 2026 |
| On Telegram | t.me/SaltSwapAnn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 12:25 | 107 | -2 |
| 9 Aug 2026, 07:31 | 109 | no change |
| 6 Aug 2026, 23:07 | 109 | first reading |
20 posts held, back to 29 April 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 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 13 February 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 27 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
SALT/BNB pool on DDDX.io is now paying up to 9928% APR
Hello SALTers! We aquired a large veNFT at DDDX exchange (https://dddx.io/). A clone of Solidly. With this aquisition we whitelisted the pool SALT/BNB on the exchange and then used all our voting power to vote for this pool and will continue doing so in the future. All the DDDX earned will be added to our veNFT to further increase our voting power. The next DDDX snapshot is happening in a few hours, after that we w…
News coming on Wednesday!
What should the next ocean be? 🌊
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
To celebrate that we got out twitter account back we will launch another ocean! pls vote on what you wanna earn
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
New CAKE OCEAN https://www.saltswap.finance/oceans Stars tomorrow at Sat Aug 28 2021 19:58:05 GMT (https://www.bscscan.com/block/countdown/10430186) Enjoy guys! 🧂
Hei! What should be the next ocean?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
In partnership with the folks at ShrimpSwap we bring to you a Whale Ocean. Starts tomorrow!
New feature. Open the ROI screen on any farm that you have staked and check the returns of your liquidity
https://twitter.com/saltswap/status/1404857174870867969?s=21
https://twitter.com/saltswap/status/1404800260376084490?s=21
Showing the 12 most recent of 20 posts we hold for @SaltSwapAnn. 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 4 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 should the next ocean be? 🌊
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
To celebrate that we got out twitter account back we will launch another ocean! pls vote on what you wanna earn
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Hei! What should be the next ocean?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
As we mentioned before. We will ask our community if we should run an IDO or not. Should we run an IDO for website: orangeswap.finance Raise Amount: 200BNB Softcap : 15 BNB Tokens Per BNB : 700 ORAGE
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 29 April 2021 to 13 February 2025. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“SaltSwap Announcements” (@SaltSwapAnn), 107 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/SaltSwapAnn.
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.