20 Nov 2024, 01:19 UTCviews —
Channel photo updated
Channel
DexPilot
@zenfuse
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002486887034 |
|---|---|
| Type | Channel |
| Username | @zenfuse |
| Created | 25 September 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zenfuse |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:46 | 7 | no change |
| 6 Aug 2026, 19:58 | 7 | first reading |
Engagement
5 posts held, back to 25 September 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 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 5 posts for this entry, the most recent from 20 November 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 12 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.
Recent posts
20 Nov 2024, 01:17 UTC65 viewsread 12 August 2026
To stay updated and join the conversation, head over to our Telegram chat at @dexpilot_chat or to our TG channel @dexpilot We can’t wait to connect with you there and share more exciting news about DexPilot’s journey forward
20 Nov 2024, 01:17 UTC55 viewsread 12 August 2026
Photo
Exciting News: Zenfuse is Now DexPilot! Dear Community, We’re thrilled to announce a big step forward: Zenfuse has rebranded to DexPilot! This change reflects our expanded vision and commitment to empowering you with a next-generation platform for decentralized trading. With DexPilot, we’re not only changing the name but enhancing our focus and innovation to deliver a stronger, more accessible experience for all ou…
25 Sept 2024, 19:10 UTCviews —
Channel photo updated
25 Sept 2024, 19:10 UTCviews —
Channel created
Showing the 5 most recent of 5 posts we hold for @zenfuse. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“DexPilot” (@zenfuse), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zenfuse.
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.