The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 9 days, that account will self-destruct and this channel may no longer have an owner.

Channel
Police Shiba Inu Announcement
@PoliceShibaInuAnnouncement
On this record: Growth · Engagement · Posts · Cite this entry
95subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001381843160 |
|---|---|
| Type | Channel |
| Username | @PoliceShibaInuAnnouncement |
| Created | Between 1 March 2018 and 29 June 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/PoliceShibaInuAnnouncement |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 07:08 | 95 | -2 |
| 9 Aug 2026, 12:02 | 97 | no change |
| 7 Aug 2026, 00:15 | 97 | first reading |
Engagement
20 posts held, back to 29 June 2021 — 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 March 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 17 days, that account will self-destruct and this channel may no longer have an owner.
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
Photo, posted without a caption
We have locked the liquidity . https://bscscan.com/tx/0xa47e355e044a5c1921c08ea6bffeb6e6ba47facd387013ca1db3e8875b8e7a8f
Our contract 0xc8ec3f37ca56649123fd028e3c079961f1be7c34
Everyone can buy now. Buy and hold for app launch.
After 7 minutes. Hold PSI and wait for our app is launch soon.
PSI will be listed on Pancakeswap after 30 minutes (Sunday, UTC+0). Buy and hold tokens and wait for our app to launch in July https://policeshiba.com =>Please visit our website for more of app details.
Already submited.
Photo, posted without a caption
PSI will be listed on Pancakeswap on July 4th 14:00 (Sunday, UTC+0). Buy and hold tokens and wait for our app to launch in July https://policeshiba.com =>Please visit our website for more of app details.
Showing the 12 most recent of 20 posts we hold for @PoliceShibaInuAnnouncement. 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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Police Shiba Inu Announcement” (@PoliceShibaInuAnnouncement), 95 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/PoliceShibaInuAnnouncement.
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.