Channel
@AV6367
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7,852subscribers
+1,627 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003909575898 |
|---|---|
| Type | Channel |
| Username | @AV6367 |
| Created | Between 1 April 2026 and 26 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 28 September 2026 |
| On Telegram | t.me/AV6367 |
Adult — 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 12 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 |
|---|---|---|
| 28 Sept 2026, 17:02 | 7,852 | +300 |
| 19 Sept 2026, 02:19 | 7,552 | +68 |
| 15 Sept 2026, 03:37 | 7,484 | +108 |
| 11 Sept 2026, 19:01 | 7,376 | +150 |
| 7 Sept 2026, 03:56 | 7,226 | +106 |
| 2 Sept 2026, 04:48 | 7,120 | +49 |
| 30 Aug 2026, 02:13 | 7,071 | +61 |
| 27 Aug 2026, 00:04 | 7,010 | +69 |
| 24 Aug 2026, 00:19 | 6,941 | +147 |
| 20 Aug 2026, 04:07 | 6,794 | +99 |
| 17 Aug 2026, 14:14 | 6,695 | +115 |
| 14 Aug 2026, 13:14 | 6,580 | +158 |
| 10 Aug 2026, 21:15 | 6,422 | +177 |
| 7 Aug 2026, 23:11 | 6,245 | +20 |
| 7 Aug 2026, 16:02 | 6,225 | first reading |
8 posts held, back to 26 July 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 9 pages 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 8 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
26 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 26 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 6 of the 8 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 26 July 2026 to 15 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🇯🇵東京/大阪必備攻略👇 出差・旅遊・放鬆・舒壓 嚴選櫻花妹・高質感體驗 適合人群：追求高品質、高級感 👑 不夜谷•高級俱樂部 💌 https://t.me/JP796 🔔 高級顧問Angelの⭐ 💌 p.gleezy.top/JP8689 🔔 高級顧問Angelの🌐 💌 https://t.me/dy947 👑 不夜谷•高級俱樂部「總覽」 t.me/addlist/t_JXv6AI6vBkMmQ1
網拍模特 每日尻尻 https://t.me/AV6367
❤5
輕操慢插 享受淫叫聲 每日尻尻 https://t.me/AV6367
#東京 Angel特推誰約誰爽系列！ 「東京✨全日空現役空姐」 資訊➡️ t.me/JP275/3409 客評1️⃣ t.me/JP859/1129 客評2️⃣ t.me/JP859/1125 客評3️⃣ t.me/JP859/1096 客評4️⃣ t.me/JP859/1074 客評5️⃣ t.me/JP859/1062 #提前預約可享第二節半價！ Angel⭐: JP8689 Angel🌐: t.me/dy947
大陸妹陳美惠京腔國語拍AV爆紅 每日尻尻 https://t.me/AV6367
❤4
🎉不夜谷五週年慶典&中秋博餅🎉 不知不覺，Angel已經在日本經營第五年了🥹 一路走來，真的非常感謝每一位支持與信任我的新朋友、老朋友，雖然這幾年間換過幾次帳號，也經歷了不少挑戰，但依然有許多陪伴了我五年的老朋友一路支持著我，這份信任我牢記於心，謝謝大家願意把朋友介紹給我，謝謝大家一次又一次的捧場，讓我的小小事業能夠一步一步走到今天 今年適逢不夜谷五週年，又迎來一年一度的中秋佳節，Angel先預祝大家中秋“佳”節快樂🌕 有句話說得好「無博餅，不中秋」又是中秋又是週年慶，怎麼能少了福利呢？ Angel特別準備了【中秋博餅大賽】依照博餅規則，不同的“科舉”對應不同的“豪禮”！ 未來Angel也會繼續努力，提供更好的服務、更優質的妹妹、更美好的體驗，謝謝大家五年的陪伴，期待未來還能和大家一起創造更多美好的回憶❤️❤️ 科舉 狀元 榜眼 探花 進士 舉人 秀才 入門博 消費10W以下2️⃣次 初級博 消費20W以下4️⃣次 中…
❤2
幹，真有料！ 每日尻尻 https://t.me/AV6367
❤5
國民寶貝 每日尻尻 https://t.me/AV6367
❤10
Showing the 8 most recent of 8 posts we hold for @AV6367. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 28 September 2026 — this entry's latest reading, not the date you are reading this.
“又尻尻2.0💨” (@AV6367), 7,852 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/AV6367.
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.