Channel
@chayanyse8
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
8,914subscribers
+71 since we began measuring on 7 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001373056760 |
|---|---|
| Type | Channel |
| Usernames | @chayanyse8 @cyysxf |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/chayanyse8 |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 26 Sept 2026, 04:42 | 8,914 | +4 |
| 25 Sept 2026, 03:59 | 8,910 | +20 |
| 17 Sept 2026, 16:21 | 8,890 | +2 |
| 17 Sept 2026, 05:59 | 8,888 | +15 |
| 14 Sept 2026, 00:00 | 8,873 | -1 |
| 13 Sept 2026, 12:55 | 8,874 | +16 |
| 9 Sept 2026, 23:58 | 8,858 | no change |
| 9 Sept 2026, 23:00 | 8,858 | +15 |
| 7 Sept 2026, 07:22 | 8,843 | no change |
| 7 Sept 2026, 06:47 | 8,843 | first reading |
4 posts held, back to 7 September 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 2 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 September 2026 |
|---|---|
| Posts held | 4 (7 September 2026 – 7 September 2026) |
| Views total | 4 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 07:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 2 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.
🔰编号：ZV3393(点击编号自动复制) 🍁一键查询验证视频🍁 麻吉H07164 省份: 贵州 城市:黔南州 年龄:18 身高:158 体重:108 罩杯:B 是否chu:否 职业:雪生 雪历:楚中 体检后能否无t:可 能否nei射:否 能否口:否 SM能不能:否 能否同居:否 能否过夜:否 能否去✈️其他省份:否 例假日期:每月中下旬 有没有纹身:否 是否抽烟🚬:是 最早出发时间:提前沟通 每月陪伴天数:2天 每月到手: 3k 个人优点:十七，好哄，见钱眼开，听话，服从度高。温柔体贴。懂事，可开朗可安静。会给你满满情绪价值。 不能接受金主:太极端 太丑 年龄太大 脾气差 强迫 冷baoli 介绍费:7888 🎗主动私聊者多数骗子注意勿上当⚠️ 🎗会员免费观看mm验证视频 🎗老板交流群🎗VIP会员权益 🎗成交反馈🎗下单流程与地区资源 🧚♀️茶颜【悦色】客服： @cyysekefu_bot
🔰编号：UZ1024(点击编号自动复制) 🍁一键查询验证视频🍁 麻吉H07162͏ 省份: 江苏 城市: 苏州 年龄︎:22͏ 身高︎:165͏ 体重︄:88 罩杯:B͏ 是︃否chu:否 职︋业︉:雪︂生 雪︇历:本︌科️ 体︇检︊后︃能否无t:可͏ 能否︎nei射:可︄ 能︅否︍口:否︅ SM能不︁能️:否 能︄否同居︂:否︋ 能否︌过︁夜︊:可︂͏ 能︀否去︋✈️其︎他省份︁:可͏ 例︃假️日︁期:月︎初︃ 有没有纹身:无︆͏͏͏ 是︆否抽︁烟︌🚬:否͏ 最︅早️出︍发︋时间︉:提︋前︄沟︀通͏ 每︁月︉陪︂伴︍天︃数︌:2-3天︌ 每月到︎手︄:1w-1.5w͏ 个人︂优点:温︎柔︆情绪稳︂定︋。可内,可无︈t,平时听︉话懂事︋。叫︅床︊好︁听︇。接︉受︀度︆高,情绪︁价︍值满满。圈子︇干…
🔰编号：XF6220(点击编号自动复制) 🍁一键查询验证视频🍁 省份:广西 城市:南宁 年龄︀:23͏ 身︇高︅:160͏ 体︃重︇:100 罩︄杯︉:75a͏ 职︀业︊:幼︉师︁ 能否︊口︇:能︍ 测试︂后能︀否无︀套︌:否︉͏ 能︄否︅飞︋外︄省︎:能 每月可︁以︂陪︎伴︁天︇数︂:3连续 是否chu:否 能否sm:否︋ 有︀没︊有纹身️:否︆ 大︊姨妈日期︍:月︋初 能︇否︌过夜︊:能͏ 能︂否同︆居︆:能︎ 生︁活︊费︂:5k 分︋几︍次支付︆零︅花︆钱︅:2 自︇我加分项︌:不找︁事,不︁爱︀生︄气,开︌朗活︈泼︌ 介绍费:7888 🎗主动私聊者多数骗子注意勿上当⚠️ 🎗会员免费观看mm验证视频 🎗老板交流群🎗VIP会员权益 🎗成交反馈🎗下单流程与地区资源 🧚♀️茶颜【悦色】客服： @cyysekef
🔰编号：NH3344(点击编号自动复制) 🍁一键查询验证视频🍁 省份:吉隆坡 城市:吉隆坡 年︎龄︉:22 身︄高︉:170 体重︊:105͏ 罩杯︉:C͏ 职︅业:xue͏ 雷︀点︋（不能︌接︊受︅）: 不︀想︉要︆事情很︀多︉的︁刁️难︄的 不︉接︉受︃小气︈的︇ 是︇否chu女️:否 例︄假日︅期:20左右︈ 体︆检︈后︆是︁否︁接︅受️🈚️tao:否︊ 可︃否︁内︅she:可（无︉套︆内︎三天︊2.5w）͏͏ 可︋否︁kou:可︎͏ 可︊否过︂夜︈:可͏͏ 可否︊同︍居:否︊ 可︍否︄异地:🉑͏ 可︎否︆飞外︂省:可︁ 能︎否︁接︈受sm: 轻微 生︄活︍费可︁否分︌2-3次支︎付️:可︍͏ 如︈果︌匹︉配︇上︀最︌快︇出︊发︉时︌间︍:沟︌通︌ 见面︉双方︎满意后︆可︇否开︋f:可︉͏ 短︈期︃…
Showing the 4 most recent of 4 posts we hold for @chayanyse8. 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.
Named by 2 registered channels — 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“茶颜【悦色】|选妃资源” (@chayanyse8), 8,914 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/chayanyse8.
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.