2026
Signed 𓆩𝙃𝙖𝙡𝙞𝙙¹⁹⁵⁹ 🇹🇷
Channel
@SiriUserBot
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
13subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001545300095 |
|---|---|
| Type | Channel |
| Username | @SiriUserBot |
| Created | 5 July 2021 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/SiriUserBot |
Gaming — 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 6 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 6 Oct 2026, 06:20 | 13 | +1 |
| 12 Aug 2026, 05:31 | 12 | no change |
| 7 Aug 2026, 04:09 | 12 | first reading |
12 posts held, back to 5 July 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 12 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
2026
Signed 𓆩𝙃𝙖𝙡𝙞𝙙¹⁹⁵⁹ 🇹🇷
Bura kaldı ya bende @GamerDasvan Fake no istiyen ulaşsın
Signed 𓆩 ᵐⁱˡˡⁱ𝙃𝙖𝙡𝙞𝙙¹⁹⁵⁹ 𓆪
.
Signed ߷ ๖ۣۜ𝙃𝙖𝙡𝙞𝙙༻⚡️ ߷
2023
Signed ߷ ๖ۣۜ𝙃𝙖𝙡𝙞𝙙 𝘼𝙧𝙙𝙖༻⚡️ ߷
Epic
Signed ߷ ๖ۣۜ𝙃𝙖𝙡𝙞𝙙 𝘼𝙧𝙙𝙖༻⚡️ ߷
epic halkı naber
2022
a
@erdembey saygılarla
https://t.me/EpicUserBot/65 Okuyun Lütfen
Siri & Hydra Ekibi Olarak Botumuzun İsmini Değiştik @EpicUserBot Artık Hydra Ekibi yapmış olduğu @epicuserbot
Channel created
Showing the 12 most recent of 12 posts we hold for @SiriUserBot. 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.
@SiriUserBot named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“epic” (@SiriUserBot), 13 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/SiriUserBot.
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.