Channel
@KIROTOLONGES
On this record: Topic ยท Growth ยท Engagement ยท Posts ยท Cite this entry
408subscribers
-28 since we began measuring on 7 August 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1003861213786 |
|---|---|
| Type | Channel |
| Username | @KIROTOLONGES |
| Created | Between 1 February 2026 and 31 July 2026 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/KIROTOLONGES |
Hacking & security โ 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 45% 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 |
|---|---|---|
| 7 Oct 2026, 20:56 | 408 | -9 |
| 26 Sept 2026, 16:02 | 417 | -6 |
| 14 Sept 2026, 10:57 | 423 | -2 |
| 7 Sept 2026, 10:38 | 425 | -1 |
| 29 Aug 2026, 02:27 | 426 | -1 |
| 22 Aug 2026, 14:55 | 427 | -3 |
| 16 Aug 2026, 02:54 | 430 | -6 |
| 8 Aug 2026, 05:16 | 436 | no change |
| 7 Aug 2026, 22:20 | 436 | first reading |
20 posts held, back to 8 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 39m 7s ๐ฑ Device: OPPO CPH2375 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 1h 10m 15s ๐ฑ Device: vivo V2317 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 30m 0s ๐ฑ Device: Infinix Infinix X6880 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 1h 0m 0s ๐ฑ Device: Infinix Infinix X6815C ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 15m 0s ๐ฑ Device: Infinix Infinix X6880 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 45m 0s ๐ฑ Device: Infinix Infinix X6815C ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 3h 25m 40s ๐ฑ Device: vivo V2317 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 30m 0s ๐ฑ Device: Infinix Infinix X6815C ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 3h 10m 40s ๐ฑ Device: vivo V2317 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 0h 15m 0s ๐ฑ Device: Infinix Infinix X6815C ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 1h 0m 0s ๐ฑ Device: vivo V2205 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
TSURUGI AUTO FEEDBACK โฑ๏ธ Playtime: 2h 55m 40s ๐ฑ Device: vivo V2317 ๐ Region: PH ๐ฎ Game: Call Of Duty Mobile Garena ๐ง Version: 1.6.56 ๐ก๏ธ Status: Safe ๐ Avail?: @Tsurugi2026 ๐ Logs: Interval Monitoring Hit
Signed kiro bot v1
Showing the 12 most recent of 20 posts we hold for @KIROTOLONGES. 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 7 October 2026 โ this entry's latest reading, not the date you are reading this.
โ9๐๐๐๐ โ(๐ณ๐ฒ๐ฒ๐ฑ๐ฏ๐ฎ๐ฐ๐ธ๐๐ต๐๐ฏ)โ (@KIROTOLONGES), 408 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/KIROTOLONGES.
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.