.
Signed sᴄɪᴇɴᴛɪsᴛ

Channel
@KingPishro
On this record: Topic · Growth · Engagement · Posts · Cite this entry
247subscribers
+7 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001085374999 |
|---|---|
| Type | Channel |
| Username | @KingPishro |
| 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 | 3 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/KingPishro |
Other / unclassifiable — 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 23 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 |
|---|---|---|
| 3 Oct 2026, 17:20 | 247 | +2 |
| 19 Sept 2026, 17:21 | 245 | +3 |
| 11 Sept 2026, 16:16 | 242 | -1 |
| 3 Sept 2026, 16:14 | 243 | +2 |
| 28 Aug 2026, 02:36 | 241 | +1 |
| 7 Aug 2026, 02:32 | 240 | no change |
| 6 Aug 2026, 00:18 | 240 | first reading |
20 posts held, back to 27 February 2018 — 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 29 May 2026. An engagement rate over an empty window would be a number about nothing.
.
Signed sᴄɪᴇɴᴛɪsᴛ
اگه کسی از قدیمیا هست بیاد پیوی @BiG_BanG
Signed sᴄɪᴇɴᴛɪsᴛ
Sticker, posted without a caption
Signed sᴄɪᴇɴᴛɪsᴛ
Video, posted without a caption
Signed sᴄɪᴇɴᴛɪsᴛ
Live stream finished (54 seconds)
Live stream started
Kiηɢ ρisнℜo pinned Deleted message
#فان😂😂😂 #پیشرو #اوج #حصین ➖➖➖➖➖➖➖➖➖➖ 👑کانال طرفداران رضا پیشرو👑 @KingPishro
Signed عسل پیشرو
عکس قدیمی و #زیرخاکیِ داش رضا و علی اوج❤️✌️ ➖➖➖➖➖➖➖➖➖➖ 👑کانال طرفداران رضا پیشرو👑 @KingPishro
Signed عسل پیشرو
Paronia Remix #ریمیکس Bahram , Ho3ein , Yas , Pishro , Kabos , Sorena #kingpishro 👑کانال طرفداران رضا پیشرو👑 @kingpishro
Signed عسل پیشرو
#شاه❤️ #پروفایل 👑کانال طرفداران رضا پیشرو👑 @KingPishro
Signed عسل پیشرو
#خدا_نزدیک_شد تویِ✊سنگ✋کاغذ✌️قیچی ... نقشِ من سنگِ😊 قیچی رو میشکنم🙂 که کاغذِ راحت شه😐 ❤ در آغوش بگیرِ سنگ و واسه بردن 🙁 سنگ,خیالش از این باخت راحته ☹️ #V18 ◼️ @kingpishro
Signed عسل پیشرو
Showing the 12 most recent of 20 posts we hold for @KingPishro. 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Kiηɢ ρisнℜo” (@KingPishro), 247 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/KingPishro.
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.