Channel
@infoh2hexpayment
On this record: Growth · Engagement · Posts · Cite this entry
236subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001099074543 |
|---|---|
| Type | Channel |
| Username | @infoh2hexpayment |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/infoh2hexpayment |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 03:36 | 236 | -1 |
| 14 Aug 2026, 09:14 | 237 | -1 |
| 7 Aug 2026, 02:33 | 238 | no change |
| 6 Aug 2026, 00:25 | 238 | first reading |
20 posts held, back to 6 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (6 August 2026 – 7 August 2026) |
| Views total | 65 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:33 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.
Axis Paket Data Owsem ✅ AXDO2 = 19.800 » 1GB + 1GB 4G + 2GB Games, 30Hari ✅ AXDO4 = 39.050 » 1GB + 3GB 4G + 4Gb Games, 30Hari ✅ AXDO8 = 46.400 » 2GB + 6GB 4G + 8GB Games, 30Hari ✅ AXDO12 = 61.600 » 3GB + 9GB 4G + 12GB Games, 30Hari Axis Paket Data Owsem Game ✅ AXDOG16 = 40.200 » 2GB+4GBMusik+6GBMlm+4GBMedsos+UnliGame, 30Hari ✅ AXDOG24 = 42.100 » 3GB+6GBMusik+9GBMlm+6GBMedsos+UnliGame, 30Hari ✅ AXDOG32 = 49.1…
Photo, posted without a caption
Axis Paket Data Mini Harian ✅ AXD1GB1 = 6.460 » 6GB+Kuota diKotamu,1Hr ✅ AXD2GB1 = 8.075 » 15GB+Kuota diKotamu,1hr ✅ AXD5GB2 = 8.462 » 5GB+Kuota diKotamu,2hr ✅ AXD8GB2 = 9.400 » 7GB+Kuota diKotamu,2hr ✅ AXD13GB2 = 12.020 » 13GB+Kuota diKotamu,2hr ✅ AXD1GB3 = 9.400 » 3GB+Kuota diKotamu,3hr ✅ AXD2GB3 = 10.750 » 5GB+Kuota diKotamu,3hr ✅ AXD4GB3 = 13.037 » 8.5GB+Kuota diKotamu,3hr…
XL Data Bebas Puas 5K 🔹XDBB5K1 = 6.500 » XL Data Bebas Puas 5K 1.8, 1HR 🔹XDBB5K2 = 10.465 » XL Data Bebas Puas 5K 3.6GB, 2HR 🔹XDBB5K3 = 15.522 » XL Data Bebas Puas 5K 5.4GB, 3HR 🔹XDBB5K4 = 21.392 » XL Data Bebas Puas 5K 7.2GB, 4HR 🔹XDBB5K5 = 26.365 » XL Data Bebas Puas 5K 9GB, 5HR 🔹XDBB5K6 = 31.977 » XL Data Bebas Puas 5K 10.8GB, 6HR 🔹XDBB5K7 …
XL Data Bebas Puas 3K 🔹XDBM3K1 = 6.500 » XL Data Bebas Puas 3K 500MB, 1HR 🔹XDBM3K2 = 7.155 » XL Data Bebas Puas 3K 1GB, 2HR 🔹XDBM3K3 = 12.130 » XL Data Bebas Puas 3K 1.5GB, 3HR 🔹XDBM3K4 = 12.544 » XL Data Bebas Puas 3K 2GB, 4HR 🔹XDBM3K5 = 15.476 » XL Data Bebas Puas 3K 2.5GB, 5HR 🔹XDBM3K6 = 18.809 » XL Data Bebas Puas 3K 3GB, 6HR 🔹XDBM3K7 = 21.586 » X…
XL Data Bebas Puas 2K 🔹XDBH2K1 = 6.500 » XL Data Bebas Puas 2K 250MB, 1HR 🔹XDBH2K2 = 4.505 » XL Data Bebas Puas 2K 500MB, 2HR 🔹XDBH2K3 = 11.700 » XL Data Bebas Puas 2K 750MB, 3HR 🔹XDBH2K4 = 9.955 » XL Data Bebas Puas 2K 1GB, 4HR 🔹XDBH2K5 = 15.167 » XL Data Bebas Puas 2K 1.25GB, 5HR 🔹XDBH2K6 = 12.670 » XL Data Bebas Puas 2K 1.5GB, 6HR 🔹XDBH2K7 = 14.456 » …
XL Data FlexMax 🔹XDFM33 = 66.495 » XL Data FlexMax 33GB Nas, 14Hari 🔹XDFM75 = 68.165 » XL Data FlexMax 75GB Nas, 14Hari 🔹XDFM50 = 78.688 » XL Data FlexMax 50GB Nas, 28Hari 🔹XDFM65 = 88.438 » XL Data FlexMax 65GB Nas, 28Hari 🔹XDFM100 = 104.038 » XL Data FlexMax 100GB Nas, 28Hari 🔹XDFM150 = 140.175 » XL Data FlexMax 150GB Nas, 28Hari 🔹XDFM250 = 188.865 » XL Data FlexMax 250GB…
Photo, posted without a caption
XL Data Flex Mini Harian 🔹XDF3G1 = 6.521 » XL Data Flex Mini 3-4GB, 1Hari 🔹XDF10G1 = 9.096 » XL Data Flex Mini 10GB, 1Hari 🔹XDF3G3 = 11.700 » XL Data Flex Mini 3,5-4,5GB, 3Hari 🔹XDF6G3 = 13.350 » XL Data Flex Mini 6-8GB, 3Hari 🔹XDF20G3 = 19.018 » XL Data Flex Mini 20GB, 3Hari XL Data Flex Mini Mingguan 🔹XDF5G7 = 14.788 » XL Data Flex Mini 4-5GB, 7Hari 🔹XDF6G7 = 18.19…
XL Data Pure 🔹XDP500 = 4.210 » Kuota 500MB, 30Hari 🔹XDP800 = 6.750 » Kuota 800MB, 30Hari 🔹XDP1000 = 8.150 » Kuota 1GB, 30Hari 🔹XDP2000 = 15.900 » Kuota 2GB, 30Hari 🔹XDP3000 = 23.650 » Kuota 3GB, 30Hari 🔹XDP4000 = 31.235 » Kuota 4GB, 30Hari 🔹XDP5000 = 39.300 » Kuota 5GB, 30Hari 🔹XDP6000 = 47.100 » Kuota 6GB, 30Hari 🔹XDP7000 = 56.950 » Kuota 7GB, 30Hari 🔹XDP…
XL Data Exterprise 🔹XDE2GB = 17.650 » Kuota 2.5GB+1,5GB DPI Apps, 7Hr 🔹XDE4GB = 22.600 » Kuota 3,5GB+1GB DPI Apps, 30Hr 🔹XDE6GB = 30.300 » Kuota 5GB+1,5GB DPI Apps, 30Hr 🔹XDE7GB = 35.300 » Kuota 5GB+2GB DPI Apps, 30Hr 🔹XDE12GB = 50.300 » Kuota 10GB+2GB DPI Apps, 30Hr 🔹XDE15GB = 50.900 » Kuota 10GB+5GB DPI Apps, 30Hr 🔹XDE25GB = 75.900 » Kuota 17GB+8GB DPI Apps, 30Hr 🔹XDE26GB = 10…
XL Data Combo Double Youtube 🔹XDC5 = 58.650 » 5GB+10GB(Youtube), 30Hr 🔹XDC10 = 87.650 » 10GB+20GB(Youtube), 30Hr 🔹XDC15 = 123.300 » 15GB+30GB(Youtube), 30Hr 🔹XDC20 = 171.300 » 20GB+40GB(Youtube), 30Hr 🔹XDC35 = 229.300 » 35GB+70GB(Youtube), 30Hr XL Data Combo VIP Double Youtube 🔹XDCV5 = 64.775 » VIP 5GB+10GB(Youtube), 30Hr 🔹XDCV10 = 92.700 » VIP 10GB+20GB(Youtube), 30Hr 🔹XDC…
Showing the 12 most recent of 20 posts we hold for @infoh2hexpayment. 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“INFO H2h Expayment” (@infoh2hexpayment), 236 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/infoh2hexpayment.
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.