Channel
@drife_official
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,502subscribers
-8 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001255243102 |
|---|---|
| Type | Channel |
| Username | @drife_official |
| Created | 28 May 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/drife_official |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:33 | 1,502 | -6 |
| 9 Aug 2026, 12:41 | 1,508 | -1 |
| 6 Aug 2026, 13:22 | 1,509 | -1 |
| 6 Aug 2026, 07:35 | 1,510 | no change |
| 6 Aug 2026, 05:52 | 1,510 | first reading |
20 posts held, back to 9 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 August 2025. An engagement rate over an empty window would be a number about nothing.
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.
The DRIFE Protocol Whitepaper is live. We’re proud to share the blueprint for a future where mobility is decentralized, trustless, and user-owned. At DRIFE, we’ve spent the last year building more than just a ride-hailing alternative — we’ve been laying the infrastructure to transform ride data into digital identity, reputation, and access. In this whitepaper, you’ll find: ✅ How ride history becomes on-chain proof…
DRIFE Update: A New Era of Mobility Is Here We’ve just dropped a powerful new blog that outlines the future of decentralized mobility — and DRIFE’s bold vision to lead it. We’re not just about booking rides anymore. We’re building the infrastructure where your ride data becomes identity, your trips earn rewards, and mobility becomes financial access. In this post: ✅ Why centralized mobility is broken ✅ How DRIFE i…
New Blog Drop: The Next Chapter of DRIFE We’re no longer just a ride-hailing app. We’re building the protocol that will power mobility, digital identity, and on-chain financial access around the world. ✅ Real rides ✅ Real data ✅ Real ownership This is Chapter 2. The future of decentralized mobility starts now. 📝 Read the vision
The new DRIFE website is LIVE! We’re not just building tech — we’re unlocking a new layer of the mobility economy. Explore how DRIFE turns your rides into on-chain identity, ownership, and rewards. 🌐 Dive in now — and stay tuned, we’re just getting started. 👉 https://www.drife.io/
We’re ready. 🔧 The pivot is complete. Next week, we go live with what’s next — the vision, the product, and the future of DRIFE. Buckle up. It’s reveal time. 🚀 #StayTuned #DRIFEReimagined
Channel photo updated
Hey DRIFERs! We’ve got an AMA coming up tomorrow! This won’t be a live session, so feel free to: ➤ Drop your questions right here ➤ Or DM @Raj_Drife directly
AMA update Today's AMA got cancelled due to poor internet connection.
https://x.com/Drife_official/status/1908043890398986406
https://x.com/Drife_official/status/1907362080715575647
https://x.com/Drife_official/status/1905546591819497838
https://x.com/Drife_official/status/1880475242138866136?t=Ql0gdgoKQP-EqkcnoeMJ7A&s=19
Showing the 12 most recent of 20 posts we hold for @drife_official. 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 — 355,885 of 1,478,351entries 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.
@drife_official 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.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Drife_official Announcements” (@drife_official), 1,502 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/drife_official.
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.