Channel
@mustikareload
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
471subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001085385885 |
|---|---|
| Type | Channel |
| Username | @mustikareload |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/mustikareload |
Ecommerce storefront — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 07:37 | 471 | +4 |
| 28 Sept 2026, 06:18 | 467 | -1 |
| 4 Sept 2026, 10:40 | 468 | +1 |
| 28 Aug 2026, 07:47 | 467 | -1 |
| 20 Aug 2026, 11:43 | 468 | -4 |
| 12 Aug 2026, 13:25 | 472 | -2 |
| 6 Aug 2026, 19:02 | 474 | no change |
| 6 Aug 2026, 00:58 | 474 | 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 page of 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
PAKET NELFON TELKOMSEL PAMASUKA ♦️PNB0 = 5.850 Telkomsel Telepon All Operator 60 Menit 1 Hari ♦️PNB1 = 5.950 Telkomsel Telepon All Operator 90 Menit 1 Hari ♦️PNB1B = 15.450 Telkomsel Telepon All Operator 1440 Menit 1 Hari ♦️PNB1A = 10.325 Telkomsel Telepon All Operator 140 Menit 3 Hari ♦️PNB2 = 17.000 Telkomsel Telepon All Operator 300 Menit 3 Hari ♦️PNB2B = 22.550 Telkomsel Telepon All Operator…
MAINTENANCE Sudah Selesai Transaksi Bisa Di Lanjut Bosku
⚠️ PERSIAPAN PROSES MAINTENANCE ⚠️ Jam 23: 40 - 00 : 30 Selama Proses Maintenance Berlangsung, All Transaksi Kami Close Transaksi Akan Kembali Normal Setelah Proses Maintenance Selesai. -Terimakasih-
AKTIVASI VOC.SUPER MINI 1-3Hr ====================== ⭕ CABB500 = Aktivasi Vocher 13GB+Kuota diKotamu,2Day = 11.909 #Turun AKTIVASI VOC. MINGGUAN 7Hr ====================== ⭕ CAW5 = ActVoc. Axis 17GB+Kuota diKotamu,7 Day = 25.628 #Turun
#UPDATE TELKOMSEL DATA COMBO ●▬▬▬ஜ۩۩ஜ▬▬▬● ❣️COMBO1 = 51.700 12GB Nas+Vision+Premium 30day+60 SMS TSEL+ tlpn TSEL 60 minute. 28Hr ❣️COMBO5 = 75.500 27GB Nas+Vision+Premium 30day+80 SMS TSEL+ tlpn TSEL 80 minute. 28Hr ❣️COMBO7 = 97.950 35GB Nas+Vision+Premium 30day+80 SMS TSEL+ tlpn TSEL 80 minute. 28Hr ❣️COMBO10 = 236.450 89GB Nas+Vision+Premium 30day+100 SMS TSEL+ tlpn TSEL 100 minute. 28Hr ❣️COMBO13 = 256.95…
➖➖➖➖➖➖➖ XL DATA ULTRA 5G+ ➖➖➖➖➖➖➖ Siap merasakan standar baru konektivitas internet? XL Ultra 5G+ hadir dengan koneksi yang lebih cepat, lebih luas, dan lebih stabil. ➡️Kecepatan hingga 500 mbps ➡️Bonus Akses Vidio Platinum ➡️Bebas roaming di 9 negara 🔹 XDULP65 = 94.200 XL Data Ultra 5G+ 65 GB 28 Hari 🔹 XDULP100 = 118.650 XL Data Ultra 5G+ 100 GB 28 Hari 🔹 XDULP150 = 142.650 XL Data Ultra 5G+ 150 GB 28 Hari …
‼️INFO NAIK HARGA ‼️ INDOSAT DATA FREEDOM BULANAN ●▬▬▬▬▬▬▬ஜ۩۩ஜ▬▬▬▬▬▬▬● 💛 IDTS3B = 30.190 #Naik⬆️ Indosat Data Freedom 3GB 28hr Mohon Maaf ijin naik ,mohon d kondisikan juragan Demi Klancaran 🙏🙏🙏🙏
THREE DATA PURE ================ 🖤THP1GB DATA 1GB 14 HARI = 9.600 🖤THP1 DATA 1,5GB 14 HARI = 10.500 🖤THP2GB DATA 2GB 14 HARI = 15.450 🖤THP2 DATA 2,5GB 14 HARI = 15.700 🖤THP3 DATA 3GB 30 HARI = 18.500 🖤THP4 DATA 4GB 30 HARI = 23.925 🖤THP5 DATA 5GB 30 HARI = 28.400 🖤THP6 DATA 6GB 30 HARI = 36.225 🖤THP7 DATA 7GB 30 HARI = 42.225 🖤THP8 DATA 8GB 30 HARI = 48.325 🖤THP9 DATA 9GB 30 HARI = 51.520 🖤THP1…
TRI DATA HAPPY BULANAN ●▬▬▬ஜ۩۩ஜ▬▬▬● ⚫️TSHP1 Three Data Happy 3GB 20 Hari = 21.660 ⚫️TSHP1A Three Data Happy 3,5GB 28 Hari = 21.900 ⚫️TSHP2 Three Data Happy 4,5GB 28 Hari = 24.375 ⚫️TSHP3 Three Data Happy 5GB 28 Hari = 29.877 ⚫️TSHP4 Three Data Happy 7GB 28 Hari = 31.565 ⚫️TSHP5 Three Data Happy 9GB 28 Hari = 34.750 ⚫️TSHP6 Three Data Happy 10GB 28 Hari = 35.950 ⚫️TSHP7 Three Data Happy 11GB 28 Hari …
Video, posted without a caption
PULSA TRANFER TRI ====================== ⭕ HTT110 = Three Transfer = 99.686 #Turun ⭕ HTT135 = Three Transfer = 121.536 #Turun ⭕ HTT140 = Three Transfer = 125.906 #Turun ⭕ HTT170 = Three Transfer = 152.126 #Turun ⭕ HTT180 = Three Transfer = 160.866 #Turun ⭕ HTT190 = Three Transfer = 169.606 #Turun
THREE PROMO ============= 🖤TH5 = 5.135 🖤TH10 = 10.127 🖤TH15 = 14.635 🖤TH20 = 19.695 🖤TH25 = 24.665 🖤TH30 = 29.490 🖤TH35 = 34.400 🖤TH40 = 39.045 ⬇️ 🖤TH45 = 44.970 🖤TH50 = 47.955 ⬇️ 🖤TH55 = 54.840 🖤TH60 = 57.935 ⬇️ 🖤TH70 = 67.495 ⬇️ 🖤TH75 = 73.400 ⬇️ 🖤TH80 = 77.055 ⬇️ 🖤TH90 = 87.910 🖤TH95 = 92.470 🖤TH100 = 93.678 ✅ Jalur Mochan X Vtri X Rita ✅ Validasi 100% ✅ Rekon H + 0 TURUN LANCAR SILAHKAN BISA
Showing the 12 most recent of 20 posts we hold for @mustikareload. 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.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“MUSTIKARELOAD” (@mustikareload), 471 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/mustikareload.
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.