Channel
@QergrppZtKw4ZTY0
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002281777233 |
|---|---|
| Type | Channel |
| Username | @QergrppZtKw4ZTY0 |
| Created | 2 January 2025 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/QergrppZtKw4ZTY0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:16 | 2 | no change |
| 7 Aug 2026, 14:29 | 2 | first reading |
11 posts held, back to 2 January 2025 — 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 11 posts for this entry, the most recent from 14 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
🖤JOKER VIP MOD PAKS ULTRA HEADSHOT %99999 💥 🌎-𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗮𝗹𝗹 𝗣𝗨𝗕𝗚 🔰-𝗚𝗟/ 𝗞𝗥/ 𝗧𝗪/ 𝗩𝗡𝗚 ⚙️-𝗣𝗨𝗕𝗚 𝗩𝗘𝗥𝗦𝗜𝗢𝗡: 𝟰.𝟭 ⭕-𝗦𝗨𝗣𝗣𝗢𝗥𝗧: 𝟯𝟮/𝟲𝟰 𝗕𝗜𝗧 ➿➿➿➿➿➿➿➿➿➿ ➥- 𝗙𝗨𝗟𝗟 𝗕O𝗗𝗬 𝗛𝗘𝗔D𝗦𝗛O𝗧 ➥- 𝗕𝗜𝗚 𝗖𝗛𝗔𝗥𝗔𝗖𝗧𝗘𝗥 ➥- 𝗥𝗘𝗔𝗟 𝗜𝗣𝗔𝗗 𝗩𝗜𝗘𝗪 ➥- 𝗖𝗢𝗩𝗘𝗥 𝗛𝗜𝗧 𝗛𝗘𝗔𝗗 ➥- 𝗔𝗨𝗧𝗢 𝗛𝗘𝗔D𝗦𝗛O𝗧 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗠𝗔𝗚𝗜𝗖 𝗕U𝗟𝗟𝗘𝗧 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗔𝗜𝗠 𝗟𝗢𝗖𝗞 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗛𝗜𝗚𝗛 𝗗A𝗠𝗔𝗚𝗘 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗛𝗘𝗔D𝗦𝗛O𝗧 𝗥𝗢𝗢𝗠 𝟭𝟬𝟬% ➥- 𝟭 𝗦𝗛O𝗧 𝗞İ𝗟𝗟 𝗠𝟮𝟰 ➥- 𝟯 𝗦𝗛O𝗧 𝗞İ𝗟𝗟𝗦 𝗠𝟰𝟭𝟲 ➥- 𝗦𝗠𝗢𝗢𝗧𝗛 𝗚𝗥𝗔𝗣𝗛𝗜𝗖𝗦 ➥- 𝗙𝗨𝗟𝗟 𝟲𝟬/𝟵𝟬/𝟭𝟮𝟬 𝗙𝗣𝗦 ➥- 𝗙𝗨𝗟𝗟 𝗢…
https://t.me/c/2312664999/87
🖤JOKER VIP MOD PAKS ULTRA HEADSHOT %99999 💥 🌎-𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗮𝗹𝗹 𝗣𝗨𝗕𝗚 🔰-𝗚𝗟/ 𝗞𝗥/ 𝗧𝗪/ 𝗩𝗡𝗚 ⚙️-𝗣𝗨𝗕𝗚 𝗩𝗘𝗥𝗦𝗜𝗢𝗡: 𝟰.𝟭 ⭕-𝗦𝗨𝗣𝗣𝗢𝗥𝗧: 𝟯𝟮/𝟲𝟰 𝗕𝗜𝗧 ➿➿➿➿➿➿➿➿➿➿ ➥- 𝗙𝗨𝗟𝗟 𝗕O𝗗𝗬 𝗛𝗘𝗔D𝗦𝗛O𝗧 ➥- 𝗕𝗜𝗚 𝗖𝗛𝗔𝗥𝗔𝗖𝗧𝗘𝗥 ➥- 𝗥𝗘𝗔𝗟 𝗜𝗣𝗔𝗗 𝗩𝗜𝗘𝗪 ➥- 𝗖𝗢𝗩𝗘𝗥 𝗛𝗜𝗧 𝗛𝗘𝗔𝗗 ➥- 𝗔𝗨𝗧𝗢 𝗛𝗘𝗔D𝗦𝗛O𝗧 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗠𝗔𝗚𝗜𝗖 𝗕U𝗟𝗟𝗘𝗧 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗔𝗜𝗠 𝗟𝗢𝗖𝗞 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗛𝗜𝗚𝗛 𝗗A𝗠𝗔𝗚𝗘 𝗜𝗡𝗖𝗥𝗘𝗔𝗦𝗘 ➥- 𝗛𝗘𝗔D𝗦𝗛O𝗧 𝗥𝗢𝗢𝗠 𝟭𝟬𝟬% ➥- 𝟭 𝗦𝗛O𝗧 𝗞İ𝗟𝗟 𝗠𝟮𝟰 ➥- 𝟯 𝗦𝗛O𝗧 𝗞İ𝗟𝗟𝗦 𝗠𝟰𝟭𝟲 ➥- 𝗦𝗠𝗢𝗢𝗧𝗛 𝗚𝗥𝗔𝗣𝗛𝗜𝗖𝗦 ➥- 𝗙𝗨𝗟𝗟 𝟲𝟬/𝟵𝟬/𝟭𝟮𝟬 𝗙𝗣𝗦 ➥- 𝗙𝗨𝗟𝗟 𝗢…
musaidimm
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Ücretli show icin müsaitim
Channel created
Showing the 11 most recent of 11 posts we hold for @QergrppZtKw4ZTY0. 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Teyit Kanalım” (@QergrppZtKw4ZTY0), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/QergrppZtKw4ZTY0.
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.