Telegram RegisterThe public register of Telegram
Telegram profile photo for DigiFinex Announcement

Channel

DigiFinex Announcement

@DigiFinexAnnouncement

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

11,353subscribers

-533 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001335114257
TypeChannel
Username@DigiFinexAnnouncement
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/DigiFinexAnnouncement

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

11,35311,88611,619.56 August 2026 — 11,886 subscribers7 August 2026 — 11,877 subscribers8 August 2026 — 11,871 subscribers9 August 2026 — 11,850 subscribers10 August 2026 — 11,843 subscribers11 August 2026 — 11,828 subscribers12 August 2026 — 11,811 subscribers13 August 2026 — 11,801 subscribers14 August 2026 — 11,793 subscribers16 August 2026 — 11,776 subscribers17 August 2026 — 11,760 subscribers18 August 2026 — 11,745 subscribers19 August 2026 — 11,731 subscribers20 August 2026 — 11,719 subscribers21 August 2026 — 11,702 subscribers23 August 2026 — 11,685 subscribers24 August 2026 — 11,660 subscribers25 August 2026 — 11,640 subscribers26 August 2026 — 11,633 subscribers28 August 2026 — 11,628 subscribers28 August 2026 — 11,616 subscribers29 August 2026 — 11,601 subscribers30 August 2026 — 11,577 subscribers31 August 2026 — 11,566 subscribers1 September 2026 — 11,548 subscribers2 September 2026 — 11,542 subscribers4 September 2026 — 11,518 subscribers7 September 2026 — 11,487 subscribers10 September 2026 — 11,436 subscribers12 September 2026 — 11,419 subscribers14 September 2026 — 11,396 subscribers15 September 2026 — 11,379 subscribers17 September 2026 — 11,353 subscribers6 August 202617 September 2026
33 measurements spanning 42 days, net -533. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,273–11,966 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 22:2011,353-26
15 Sept 2026, 21:4111,379-17
14 Sept 2026, 02:4211,396-23
12 Sept 2026, 12:1611,419-17
10 Sept 2026, 12:0111,436-51
7 Sept 2026, 10:1911,487-31
4 Sept 2026, 16:1611,518-24
2 Sept 2026, 23:0411,542-6
1 Sept 2026, 21:5811,548-18
31 Aug 2026, 19:1311,566-11
30 Aug 2026, 22:2711,577-24
29 Aug 2026, 23:5211,601-15
28 Aug 2026, 21:5611,616-12
28 Aug 2026, 00:2411,628-5
26 Aug 2026, 21:4311,633-7
25 Aug 2026, 18:4911,640-20
24 Aug 2026, 20:5411,660-25
23 Aug 2026, 09:5511,685-17
21 Aug 2026, 20:5311,702-17
20 Aug 2026, 20:2811,719first reading

Engagement

32 posts held, back to 25 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 45 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.09%
avg views ÷ 11,353 subscribers
Avg views / post
124
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 32 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held32 (25 June 20262 September 2026)
Views total124
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 23:42 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 32 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 32 most recent posts we hold, published 25 June 2026 to 2 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Sept 2026, 05:33 UTC124 viewsread 2 September 2026
Photo

⚠️[Trading Maintenance]-Temporary Closure of the All Spot Trading Pairs Dear users, DigiFinex will suspend the trading service of all Spot trading pairs due to System Upgrade. Please note that during the maintenance upgrade, functionalities such as price updates, buying and selling, placing and canceling orders for all spot trading pairs will be temporarily unavailable. Other services will not be affected. The mai

20 Aug 2026, 03:00 UTC702 viewsread 2 September 2026
Photo

⚠️[Delisting]- Announcement on the Delisting of BRETT and RENDER Dear Users, DigiFinex will delist the following trading pairs in accordance with our Token Delisting Rules: 1. BRETT/USDT – trading, deposit and withdrawal services close at 09:00 UTC on Sep 20 2026. Withdrawals after the deadline incur a 50 USDT custody fee. 2. RENDER/USDT – trading closes at the same time; please cancel any open orders now. All rem

20 Aug 2026, 00:45 UTC294 viewsread 2 September 2026
Photo

⚠️[Trading Maintenance] - Maintenance of Certain Spot Trading Pairs on DigiFinex Dear users, In order to enhance user experience, DigiFinex will be conducting system maintenance. We will be performing maintenance on certain spot trading pairs. During this period, the relevant trading pairs will be unable to trade normally. The specific maintenance schedule is as follows: Start Time: August 22, 2026, 17:00 (UTC) Es

18 Aug 2026, 08:04 UTC739 views1 reactionsread 2 September 2026
Photo

📣 USDT High-Yield Earn Is Live: Up to 9.5% Annualized Rate with a 10 Million USDT Quota! Flexible Earn • 30/60/90-Day Fixed Terms The DigiFinex limited-time Earn event is now live! 🔥 ⏰ Event Period: August 17–August 30 💰 The total product quota reaches 10,000,000 USDT, providing ample capacity for different portfolio sizes. ✅ Flexible Earn ▫️Flexible deposits and withdrawals with hourly interest calculation ▫️Ti

1

15 Aug 2026, 14:34 UTC499 viewsread 2 September 2026
Photo

⚠️[Delisting] - Announcement Regarding the Delisting of Certain Spot Trading Pairs Dear Users, DigiFinex will delist the following tokens/pairs under our Token Delisting Rules. **CORGIAI/USDT** – Trading, deposit and withdrawal close at 9:00 UTC on Sep 14 2026. After this time a 50 USDT custody fee applies. Tokens to be delisted: 1. EGO/USDT 2. MUBI/USDT 3. SGB/USDT 4. KEEP/USDT 5. SERAPH/USDT 6. WZRD/USDT 7. PRI

14 Aug 2026, 01:18 UTC321 viewsread 2 September 2026
Photo

⚠️[Trading Suspend]Announcement Regarding Maintenance of Certain Spot Trading Pairs Dear users, Due to a system upgrade, DigiFinex will perform maintenance on the following spot trading pairs on August 14, 2026, at 06:00 UTC. The maintenance is expected to last about 30 minutes; the exact resumption time will be announced later. Affected pairs: - BTC/USDT - ETH/USDT - FIL/USDT We apologize for any inconvenience a

13 Aug 2026, 02:44 UTC461 views1 reactionsread 2 September 2026
Photo

⚠️[Delisting] - Announcement Regarding the Delisting of Certain Spot Trading Pairs Dear Users, DigiFinex will delist the following tokens and trading pairs due to rule violations or high risk: 1. XLAB/USDT – trading and deposit close at 09:00 UTC Sep 13 2026; withdrawals close at the same time. 2. A8/USDT 3. AIOZ/USDT 4. BOBA/USDT 5. BONE/USDT 6. CAT/USDT 7. HOUSE/USDT 8. MOG/USDT 9. PONKE/USDT 10. PUFFER/USDT Pl

1

11 Aug 2026, 06:23 UTC277 viewsread 2 September 2026
Photo

⚠️[Trading Suspend]Announcement Regarding Maintenance of Certain Spot Trading Pairs Dear users, Due to a system upgrade, DigiFinex will perform maintenance on the following spot‑trading pairs on August 11 2026 at 06:30 UTC. The maintenance is expected to last 30 minutes; the exact resumption time will be announced later. Trading pairs: STRK/USDT TIA/USDT CRO/USDT NEAR/USDT AAVE/USDT PEPE/USDT TRX/USDT ENA/USDT LTC

10 Aug 2026, 09:41 UTC333 viewsread 2 September 2026
Photo

⚠️[Margin trading Pair Delisting]Announcement Regarding the Delisting of Certain Leveraged Trading Pairs Dear Users, DigiFinex will delist the following margin‑trading pairs to improve market health and liquidity. **Closing times (UTC)** - 08:30 on 13 Aug 2026: SUI/USDT, XRP/USDT, XLM/USDT, SOL/USDT - 06:00 on 14 Aug 2026: BTC/USDT, ETH/USDT, FIL/USDT Please cancel any open orders before the listed times. Uncance

10 Aug 2026, 09:16 UTC181 viewsread 2 September 2026
Photo

⚠️[Margin trading Pair Delisting]Announcement Regarding the Delisting of Certain Leveraged Trading Pairs Dear Users, DigiFinex will delist the following margin‑trading pairs to improve market health and liquidity. **Closing times (UTC)** - 08:30 on 13 Aug 2026: SUI/USDT, XRP/USDT, XLM/USDT, SOL/USDT - 06:00 on 14 Aug 2026: BTC/USDT, ETH/USDT, FIL/USDT Please cancel any open orders before the listed times. Uncance

10 Aug 2026, 08:51 UTC145 viewsread 2 September 2026
Photo

⚠️[Margin trading Pair Delisting]Announcement Regarding the Delisting of Certain Leveraged Trading Pairs Dear Users, To maintain a healthy digital‑asset environment, improve liquidity and trading experience, DigiFinex will delist the following margin‑trading pairs: STRK/USDT, TIA/USDT, CRO/USDT, NEAR/USDT, AAVE/USDT, PEPE/USDT, TRX/USDT, ENA/USDT, LTC/USDT, VET/USDT, DOGE/USDT Trading will close at 06:30 UTC on A

Showing the 12 most recent of 32 posts we hold for @DigiFinexAnnouncement. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Dex-Trade Channel
@Dex_Trade · 67,342
Telegram ranks this channel #7 of 90 here — alongside 89 others — read 21 August 2026
XT Exchange Announcements
@XTannouncements_EN · 31,836
Telegram ranks this channel #11 of 55 here — alongside 54 others — read 5 September 2026
PAXGold Channel
@PAXGold_Channel · 54,050
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 23 August 2026
Toobit Announcements
@Toobit_announcements · 39,597
Telegram ranks this channel #42 of 91 here — alongside 90 others — read 3 September 2026
BitMart Exchange Channel
@BitMartExchange_Channel · 60,370
Telegram ranks this channel #48 of 81 here — alongside 80 others — read 21 August 2026
Airdrop Broadcaster
@AirdropBroadcasterCom · 49,641
Telegram ranks this channel #70 of 88 here — alongside 87 others — read 25 August 2026
Airdrop Presents 🗽
@airdrop_Presents · 200,391
Telegram ranks this channel #72 of 82 here — alongside 81 others — read 11 August 2026
AirdropAlert-com | Crypto Airdrops for Everyone
@airdrop_alert_dot_com · 194,993
Telegram ranks this channel #86 of 90 here — alongside 89 others — read 20 August 2026

This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“DigiFinex Announcement” (@DigiFinexAnnouncement), 11,353 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/DigiFinexAnnouncement.

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.