🌈Line:mt160/bk638 🌈Gleezy:mt160 🌈Telegram:@mt1689 營業時間: 13:00~4:00 📌商城下次Gleezy選妃交流群組:https://c.gleezy.top/4nuZaI0L 🍀北部專區:@mt1678 🍀中部專區:@mt03344 🍀南部專區:@mt16890 🍀新竹專區:@mt1650 🍀學生妹18~22歲:@mt16990 🍀大奶巨乳熟女:@mt16789 🍀人妻熟女專區:@mt5271 #台灣外送茶 #台灣出差找小姐 #高檔茶 #學生妹試車 #旅館一夜情 #口碑茶 #無套內射 #巨乳

Channel
自拍🔞成人A片频道
@av2978
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
345subscribers
-16 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 | -1002872350282 |
|---|---|
| Type | Channel |
| Username | @av2978 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/av2978 |
Topic
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 23:14 | 345 | -1 |
| 18 Sept 2026, 15:19 | 346 | -5 |
| 9 Sept 2026, 15:01 | 351 | -4 |
| 30 Aug 2026, 09:06 | 355 | -3 |
| 15 Aug 2026, 16:26 | 358 | -3 |
| 8 Aug 2026, 06:33 | 361 | no change |
| 7 Aug 2026, 19:05 | 361 | first reading |
Engagement
1 post held, back to 6 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 1 post for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 1 most recent of 1 post we hold for @av2978. 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.
Mentions
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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“自拍🔞成人A片频道” (@av2978), 345 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/av2978.
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.