❗️ NAVI (NAVI) Jumps +7.01% 📈 NAVI/USDT = 0.000168 ❗️DION (DION) Jumps +4.59% 📈 DION/USDT = 0.005951 ❗️ Swingby (SWINGBY) Jumps +3.71% 📈 SWINGBY/USDT = 0.0810
Signed Navibration

Channel
@NAVIBRATION_Announcements
On this record: Growth · Engagement · Posts · Citations · Cite this entry
58subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001235513605 |
|---|---|
| Type | Channel |
| Username | @NAVIBRATION_Announcements |
| Created | Between 1 March 2018 and 22 October 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/NAVIBRATION_Announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:39 | 58 | -1 |
| 10 Aug 2026, 05:46 | 59 | no change |
| 7 Aug 2026, 22:34 | 59 | first reading |
20 posts held, back to 22 October 2019 — 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 22 January 2021. An engagement rate over an empty window would be a number about nothing.
❗️ NAVI (NAVI) Jumps +7.01% 📈 NAVI/USDT = 0.000168 ❗️DION (DION) Jumps +4.59% 📈 DION/USDT = 0.005951 ❗️ Swingby (SWINGBY) Jumps +3.71% 📈 SWINGBY/USDT = 0.0810
Signed Navibration
Dear community, We wish you a Happy New Year 2021 full of success and health. 2020 has been a difficult year for everyone, but the Navibration project keeps on progressing with the objective of becoming the new way of discovering the world when all this finishes and we can go out to enjoy and explore everything around us once again. The following audio tours will be available in our catalogue soon: - Berlin - Dub…
Signed Navibration
Dear community, We hope that you are all safe and healthy. Despite the difficulties that we are finding on the way, the Navibration project continues to move forward and we are trying to face important milestones within the next few months. One of our main objectives is to create a new way of discovering the cities after COVID-19, turning your smartphone into your personal guide; in other words, it will be like do…
Signed Navibration
Dear community, These are being difficult days for the entire world and we hope you are all safe and healthy. Now it is time to stay at home but hopefully we will get back to the "new normality" soon and Navibration will be there to offer a new way of discovering the cities while walking around them. We continue working on the project and new audio tours from amazing cities will be announced soon! Stay tuned!
Signed Navibration
Dear community, After a few weeks of absence, we would like to tell you that the project development is going ahead and many more cities will be available within the app soon. On the other hand, we are working on a new version in which the token will play an important role and token holders will benefit. Stay tuned!
Signed Navibration
Merry Christmas and happy NAVI trading! Currently, a stunning +300%!!!
Signed Navibration
NAVI reaches top 7 trading volume on ProBit!!! Thanks everyone supporting NAVI!
Signed Navibration
Amazing NAVI trading on ProBit!!! Thank you everyone supporting NAVI!
Signed Navibration
Dear community, The Navibration project continues to progress and we are currently exploring amazing partnerships with some top-notch companies that we cannot disclose yet. Moreover, we are preparing a new version of our app, in which some key features will be only accessible to token holders. So we go on working as hard as possible to achieve important goals and try to recover the token price soon. Stay tuned!
Signed Navibration
NAVIBRATION - News pinned «NaviCoin (NAVI) trading on ProBit Exchange is now live! Do not miss the amazing trading competition held for NAVI on ProBit Exchange: https://support.probit.com/hc/en-us/articles/360035556552-NaviCoin-NAVI-Trading-Competition-»
NaviCoin (NAVI) trading on ProBit Exchange is now live! Do not miss the amazing trading competition held for NAVI on ProBit Exchange: https://support.probit.com/hc/en-us/articles/360035556552-NaviCoin-NAVI-Trading-Competition-
Signed Beatriz | Navibration.com
NAVIBRATION - News pinned «NaviCoin (NAVI) trading on ProBit Exchange will start in less than 9 hours! A trading competition will be held for NAVI on ProBit Exchange and a total of 500,000 NAVI will be distributed to the Top 10 volume traders, so do not miss this amazing opportunity!…»
Showing the 12 most recent of 20 posts we hold for @NAVIBRATION_Announcements. 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.
Citation-graph rank — 1,298,751 of 1,481,217entries 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“NAVIBRATION - News” (@NAVIBRATION_Announcements), 58 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/NAVIBRATION_Announcements.
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.