有事还没回来不一一回复了,回来会通知宝贝们

Channel
依娜🏠
@dinnxks5
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
259subscribers
+1 since we began measuring on 3 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004470056851 |
|---|---|
| Type | Channel |
| Username | @dinnxks5 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 November 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/dinnxks5 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 05:31 | 259 | +1 |
| 3 Nov 2026, 11:22 | 258 | first reading |
Engagement
16 posts held, back to 28 October 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.
- ERR · 30 days
- 157.6%
- avg views ÷ 259 subscribers
- Avg views / post
- 408
- 16 posts measured
- Reaction rate
- 0.189%
- reactions ÷ views · ER floor
- Posts in window
- 16
- of 16 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. It is computed over the 5 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 16 (28 October 2026 – 1 November 2026) |
| Views total | 6,529 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 11: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.
What this channel posts
- Video runtime
- 10s
- Average length
- 10s
Measured directly from 1 video 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.
Reaction mix
5 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 80.0% | |
| 💩 | 1 | 20.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 5 of the 16 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 28 October 2026 to 1 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 16 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
明天后天有事不开哦
#投稿 🌍光之国反馈报告 🌍出击英雄TG:(你的TG号) 🌍拯救老师TG:林依娜(老师TG号) 🌍位置: #官渡区 🌍ls课表相似度:高(高 / 中 /低) 🌍体验项目:一次 (一次 / 两次 /✌️) 🌍ls优点:胸真的很不错,看着有C而且很挺,身材也很好,紧致 🌍ls缺点:可惜没有皮肤,喜欢皮肤的老哥可能要自带 🌍PS补充说明: 🌍是否推荐:推荐 📨 投稿机器:@DiJiaTouGaobot ⚠️ 投稿须知(请认真阅读): 1️⃣ 投稿需 上传出击证明(约课记录) 与 出击照片(须经老师同意后拍摄)。 2️⃣ 所有投稿将由人工审核上传,请务必真实、客观。 如发现 伪造车评或虚假反馈,一经核实,投稿人及相关老师将被移除处理。 光之国:https://t.me/DiJaoooo7 📸福利:https://t.me/DiDiDij9 【复制模版投稿 如不则审核不通过】 from 匿名
休息中
黑丝白丝都有哦
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179310158961 🎰 童颜巨乳林依娜频道大放送🎉🎉🎉 ⚠️ 抽奖说明: 参与者必须关注老师频道,中奖者与老师沟通时间,3天内完成出击并提交车评 💁 参与情况:170达标 / 186报名 🎅 联系领奖:C(人生大事做准备上... 1. t t 奖品:单p半价优惠 祝大家心想事成好运连连!
有空哦
——✨个人主页✨—— 老师名称: #林依娜 榜单编号: #红尘榜 0394 ——💕基础资料💕—— 地区: #昆明,#官渡区 年龄: #嫩妹 类型: #腿控,#足控,#胸控 服务: #舌吻,#69,#口交,#陪浴,#情趣,#丝袜 投票排名: ——🫧约课标准🫧—— 价格:#7P #13PP 联系老师:林依娜 其他联系:双向: @ixndndkxn_bot ——💌综合评价💌—— 综合评分:8.71 总评价数:6 人照评分:9.00 颜值评分: 8.83 身材评分:9.42 服务评分:8.17 情绪价值:8.50 环境评分:8.33 ❤️好评率:100% 💔差评率:0% 🌷评价林依娜 ✅全部评价
现在空哦
😊😊😊
❤1
#投稿 🌍光之国反馈报告 🌍出击英雄TG:杨二 🌍拯救老师TG:@hhfbnnb 🌍位置: 官渡区 🌍ls课表相似度:高 🌍体验项目: 一次 🌍ls优点:身材好,甜妹,嫩,户型也好,jio也好看,哪哪都好 🌍ls缺点:无 🌍PS补充说明:简直完全符合我xp !! 🌍是否推荐:特别推荐! 📨 投稿机器:@DiJiaTouGaobot ⚠️ 投稿须知(请认真阅读): 1️⃣ 投稿需 上传出击证明(约课记录) 与 出击照片(须经老师同意后拍摄)。 2️⃣ 所有投稿将由人工审核上传,请务必真实、客观。 如发现 伪造车评或虚假反馈,一经核实,投稿人及相关老师将被移除处理。 光之国:https://t.me/DiJaoooo7 📸福利:https://t.me/DiDiDij9 【复制模版投稿 如不则审核不通过】 from 杨 二
❤2
#投稿 🌍光之国反馈报告 🌍出击英雄TG:哥布林 🌍拯救老师TG:林依娜 🌍位置: 官渡区 🌍ls课表相似度:只忙着揉奶子了,该有的都有 🌍体验项目: 一次 🌍ls优点:奶子大!奶子挺!奶头小!奶子看得到青筋! 🌍ls缺点:床上叫爸爸,下了床就叫我小趴菜 🌍PS补充说明:林依娜回来了,被她逗的火起,冲过去就是一顿揉,一边揉一边舔,去的兄弟们可以试试整张脸埋到少女奶子里的感觉。然后让她随便口了两下,就一边揉一边操,小逼挺热的这个要加分,水也阔以的。日到她说你不是说你很快吗?被这个搞笑女又气一次,猛猛搞两下搞到她叫爸爸顺利出货。走的时候又抱又摸的,要不是没时间高低我再揉一小时。 🌍是否推荐:推荐 📨 投稿机器:@DiJiaTouGaobot ⚠️ 投稿须知(请认真阅读): 1️⃣ 投稿需 上传出击证明(约课记录) 与 出击照片(须经老师同意后拍摄)。 2️⃣ 所有投稿将由人工审核上传,请务必真实、客观。 如发现…
💩1
Showing the 12 most recent of 16 posts we hold for @dinnxks5. 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.
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.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“依娜🏠” (@dinnxks5), 259 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/dinnxks5.
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.