Telegram RegisterThe public register of Telegram

Channel

琴儿的频道

@qinera2

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

155subscribers

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004410602670
TypeChannel
Username@qinera2
CreatedBetween 1 June 2026 and 13 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held1
On Telegramt.me/qinera2

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:01155first reading

Engagement

8 posts held, back to 13 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
170.2%
avg views ÷ 155 subscribers
Avg views / post
264
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 8 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held8 (13 August 202614 August 2026)
Views total1,319
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 22:01 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.

What this channel posts

Photos
19
Videos
12
Links
5

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
41s
Average length
10s

Measured directly from 4 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.

Recent posts

14 Aug 2026, 10:13 UTC178 viewsread 14 August 2026
Forwarded from @CQCBDRZPhoto

✡️重庆茶百道楼凤总榜推荐 ⭐️【花名】#琴儿 ⭐️【联系】@qinera1 ⭐️【频道】@qinera2 ⭐️【位置】江北 ⭐️【标签】 #少御 #鸳鸯浴 #嘟龙 #口豹 #AB面 #双飞 ⭐️【价格】7p13pp ⭐️【补充】少御老师琴儿,无纹身身材极品,性格温柔听话情绪价值高,喜欢女友感服务可冲!!! 🐴重庆茶百道楼凤总群: https://t.me/CQCBD

13 Aug 2026, 12:17 UTC272 viewsread 14 August 2026

💯 车评系统 | 评价模版 当前模版 【时间】:2026-08-13 【老师】:琴儿 【留名】:苟富贵 【人照】:9 【颜值】:9 【身材】:9 【服务】:9 【态度】:9 【环境】:9 【报告出处】:重庆封神榜:https://t.me/fsbbyq666 【过程】:心血来潮了想找个嫩妹出击一下,看到妹妹的报告,兄弟们给的评价挺好,于是抱着试一试的心态找到妹妹。进门后,妹妹真的很漂亮啊,身材也好,非常热情,我果断缴了水费,脱下衣服,妹妹拉着我洗澡,洗完澡后,妹妹帮忙擦干身子,然后慢慢开始调情,妹妹的口活真的一绝,舌头灵活有力,而且妹妹口的非常好,无齿感,非常舒服。所有服务真的很用心,很主动,每次都把我搞的硬邦邦,而且非常健谈。先是在床上搞了几下,变换了好几个姿势,叫声迷人,我也不知道她高没高潮,反正妹妹下面水越来越多,我也越来越兴奋,随后就是忍不住射了。临走前和妹妹抱抱,吻别。非常不错的一次体验,妹妹情绪价值很高,喜欢嫩妹的

Showing the 8 most recent of 8 posts we hold for @qinera2. 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.

Citation-graph rank

Citation-graph rank — 853,142 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“琴儿的频道” (@qinera2), 155 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qinera2.

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.