27 measurements spanning 30 days, net -120. 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,729–11,886 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)
Subscribers
Change
6 Sept 2026, 16:42
11,747
-20
4 Sept 2026, 04:17
11,767
-10
2 Sept 2026, 15:36
11,777
-3
1 Sept 2026, 18:18
11,780
-13
31 Aug 2026, 18:02
11,793
-1
30 Aug 2026, 20:49
11,794
-3
29 Aug 2026, 21:04
11,797
-5
28 Aug 2026, 17:58
11,802
-10
27 Aug 2026, 20:17
11,812
+4
26 Aug 2026, 21:14
11,808
+8
25 Aug 2026, 23:42
11,800
-4
25 Aug 2026, 01:59
11,804
-18
23 Aug 2026, 14:27
11,822
-25
21 Aug 2026, 21:36
11,847
-7
20 Aug 2026, 14:16
11,854
-2
19 Aug 2026, 14:44
11,856
-12
18 Aug 2026, 13:44
11,868
+9
17 Aug 2026, 10:39
11,859
+12
14 Aug 2026, 07:55
11,847
+5
13 Aug 2026, 03:34
11,842
first reading
Engagement
196 posts held, back to 4 August 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 51 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
4.30%
avg views ÷ 11,747 subscribers
Avg views / post
505
165 posts measured
Reaction rate
0.274%
reactions ÷ views · ER floor
Posts in window
165
of 196 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. It is computed over the 66 of 165 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 September 2026
Posts held
196 (4 August 2026 – 2 September 2026)
Views total
83,361
Reactions total
100
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 00:52 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
122 reactions across 68 posts, in 5 distinct kinds. The most used accounts for 79.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
97
79.5%
🔥
15
12.3%
🤯
7
5.74%
👍
2
1.64%
🤣
1
0.82%
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 78 of the 196 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 122 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 196 most recent posts we hold, published 4 August 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.
WHEN CONNECTED REACT FOR MORE 🐐
FEEDBACK FOR MORE
ENJOY 🐐
Stay connected with us 🐐
Join and stay tuned
https://t.me/WORLDWILDINTERNETTECH
https://t.me/worldwildinternetandmore
÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷
WHEN CONNECTED REACT FOR MORE 🐐
FEEDBACK FOR MORE
ENJOY 🐐
Stay connected with us 🐐
Join and stay tuned
https://t.me/WORLDWILDINTERNETTECH
https://t.me/worldwildinternetandmore
÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷÷
Join For More Lifetime Files
Group: @GreatNationOfBrothers
Channel: @Tls_TunnelFiles
Signed 𝐀 𝐍 𝐎 𝐍 𝐘 𝐌 𝐎 𝐔 𝐒ツ 𝐊29
Showing the 12 most recent of 196 posts we hold for @Ha_tunnel305. 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
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.
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
6
handles named in this channel’s posts, vacant today
Evidenced gone
4
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@Ha_tunnel305 named 6 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.
@gp_plugs named in 46 posts, 8 August 2026 – 2 September 2026 · confirmed gone 4 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@outlaws_nwa named in 21 posts, 8 August 2026 – 22 August 2026 · confirmed gone 23 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@chanel_on_sa named in 4 posts, 2 September 2026 – 3 September 2026 · confirmed gone 27 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mrslimenet named in 1 post, 22 August 2026 – 22 August 2026 · confirmed gone 23 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.
@tyson_world named in 3 posts, 8 August 2026 – 10 August 2026
@whatsapp named in 3 posts, 8 August 2026 – 10 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 6 September 2026 — this
entry's latest reading, not the date you are reading this.
“Ha tunnel plus RSA🇿🇦 ALLNET Files” (@Ha_tunnel305), 11,747 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/Ha_tunnel305.
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.