4 measurements spanning 6 days, net -24. 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 3,514–3,546 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 01:47
3,518
-13
11 Aug 2026, 02:23
3,531
-11
7 Aug 2026, 20:01
3,542
no change
7 Aug 2026, 19:08
3,542
first reading
Engagement
8 posts held, back to 2 January 2026 — 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.
ERR · 30 days
3.04%
avg views ÷ 3,518 subscribers
Avg views / post
107
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 8 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
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
8 (2 January 2026 – 5 August 2026)
Views total
107
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 20:01 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.
What this channel posts
Video runtime
52s
Average length
52s
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.
NEW UPDATE 3.0 BAILEYS🍙
RECOMENDED BAILEYS✅
"@whiskeysockets/baileys": "github:dilxzcode/bails",
CLICK TEXT TO COPY😽
KEUNTUNGAN UPDATE🤖
• support all type msg
• support all whatsapp
• support all script bot
• support node js 20-24
• support custom pairing
• no log out connection
• no error pairing code
📢TUTORIAL PASANG BAILEYS!!
• Buka File package.json Cari Ini
"@whiskeysockets/baileys": "github:123/456",
• Setelah…
🤩 𝗔𝗖𝗖𝗢𝗨𝗡𝗧 𝗢𝗪𝗡𝗘𝗥𝗦
➡️ Name : ϟ Dilxz Official
➡️ Username : @dilxzcode
⚠️ Note : The original account only has the username above, other than the telegram above, it is definitely a scammer.
Dear Telegram App Owner @durov and Telegram Support Team @telegram,
I @dilxzcode, the owner of a Telegram channel under the name @dilxzshop, would like to apply to prevent the blocking of our channel. We are committed to complying with all policies and guidelines set by Telegram.
Our channel aims to store all the proof of my transactions with my customers. We really appreciate the Telegram platform as a means of co…
Showing the 8 most recent of 8 posts we hold for @dilxzshop. 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.
Handles this channel named that no longer answer
Dead references
5
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@dilxzshop named 5 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@than_xs named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 15 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@dilxzxiros named in 2 posts, 8 August 2026 – 8 August 2026
@deniss_erorr named in 1 post, 8 August 2026 – 8 August 2026
@niccww named in 1 post, 8 August 2026 – 8 August 2026
@xlwylubi named in 1 post, 8 August 2026 – 8 August 2026
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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“- DilxzOfficial !” (@dilxzshop), 3,518 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dilxzshop.
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.