Telegram RegisterThe public register of Telegram
Telegram profile photo for 吉伊的小屋

Channel

吉伊的小屋

@lingnabeierxw

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

1,983subscribers

+180 since we began measuring on 12 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002250256017
TypeChannel
Username@lingnabeierxw
CreatedBetween 1 August 2024 and 31 January 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 September 2026
Last confirmed live18 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/lingnabeierxw

Growth

1,8031,9831,89312 September 2026 — 1,803 subscribers13 September 2026 — 1,893 subscribers18 September 2026 — 1,983 subscribers12 September 202618 September 2026
3 measurements spanning 6 days, net +180. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,776–2,010 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 11:561,983+90
13 Sept 2026, 19:581,893+90
12 Sept 2026, 09:221,803first reading

Engagement

10 posts held, back to 3 July 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.1%
avg views ÷ 1,983 subscribers
Avg views / post
201
4 posts measured
Reaction rate
0.203%
reactions ÷ views · ER floor
Posts in window
4
of 10 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 2 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 September 2026
Posts held10 (3 July 202612 September 2026)
Views total802
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Sept 2026, 09: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
26s
Average length
9s

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

Reaction mix

11 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 72.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
872.7%
🥰327.3%

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 7 of the 10 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 3 July 2026 to 12 September 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

12 Sept 2026, 07:03 UTC188 viewsread 12 September 2026
Video

🎰 徐汇颜值嫩妹【吉伊】@lnbeier 福利劵 📮 参与条件 🪪 必须设置用户名 🎫 加入-上海艺术展览会备用群 🎫 加入-吉伊的小屋 🎫 加入-上海艺术展览会交流群 🎫 加入-上海艺术展览会榜单 🎫 加入-上海艺术展览会人气推荐榜 🎫 加入-上海艺术展览会报告区2.0 🎁 奖品名单 💰️ 200通用劵 × 5 📜 抽奖说明 中奖者截图发给老师兑换 @lnbeier 开奖后3天内完成出击 如特殊情况可延后 优惠劵获得者出击后必须写报告完不成请勿报名(近期没有上课意向的狼友 请勿参与 不去联系管理报备说明原因) ‼️报告要求 不能三言两语的敷衍,体验情况要写明 ‼️禁止转让私下交易(如发现全网封杀) 点击查看【吉伊】个人资料:⬇️ https://t.me/yishuzanlanhui/36347 📆 开奖时间 • 北京时间 2026-09-15 18:01

11 Sept 2026, 06:18 UTC313 views0 reactionsread 12 September 2026
Forwarded from @chasesh_xlbPhoto

😀 野寻超级现金福利互推活动强势来袭~😀 最高可获2️⃣8️⃣8️⃣8️⃣8️⃣元 😀 如何参加? 😀 在野寻榜单老师实付累计满1000元; 😀 消费后在野寻提交本人真实评价; 😀 审核通过后进入活动颁奖群。 🎯连续30天领取每日红包,累计“尾1”红包: 1️⃣0️⃣个“尾1” →6️⃣个名额 💴8️⃣8️⃣8️⃣+8️⃣0️⃣0️⃣0️⃣储值卡 1️⃣1️⃣个“尾1” →3️⃣个名额 💴3️⃣8️⃣8️⃣8️⃣+1️⃣0️⃣0️⃣0️⃣0️⃣储值卡 1️⃣2️⃣个“尾1” →1️⃣个名额 💴8️⃣8️⃣8️⃣8️⃣+2️⃣0️⃣0️⃣0️⃣0️⃣储值卡 ❤️奖励名额先到先得; 🧪按最高档领取,不重复叠加。 4⃣️ 活动时间 活动报名开启时间:北京时间2026年08月27日22:00 活动方案:https://t.me/chasesh_xlb 上海交流:https://t.me/chasesh_jlq 上海报名 : 野寻

4 Aug 2026, 02:53 UTC≈1,990 views1 reactionsread 12 September 2026
Video

Video, posted without a caption

1

1 Aug 2026, 08:40 UTC≈1,800 views2 reactionsread 12 September 2026

刚刚cj完回到家,一边回味一边写下这篇好评(老师没有催我写,完全是自来水)。对于吉伊老师,出发前还是挺忐忑的,怕驾照怕机车怕没服务,而且这两年水费跟内存硬盘一样普遍价格飙涨,一次性丢出去1500块还没啥好体验的话还是挺心疼的。 不过这一切担忧都在推门而进,看到从门后探出一个娇俏脑袋时的那一刻烟消云散。 具体过程不详述了,ly们自行体验。这里只列一下老师的优缺点: 1. 人照8-9分吧,见仁见智,个人感觉只是p了一下脸型,整体区别不大。属于高颜嫩妹。说是刚满20,看上去像是17-18岁可爱的女孩子 2. 老师皮肤偏暖白,肤质很好 ,而且浑身都是香香的,包括小妹妹,哪哪亲起来都很有感觉 3. 三点式服务,但是时长和互动都很到位。会主动询问要不要69,69做了大概得有3、5分钟,不催 4. 女上很卖力,一直摇到没力了才停。小学里很热很润,吊感一流。换了女上,后入,cjs几个姿势,配合度高,后悔没有尝试抱起来火车便当。 5. 可以🐍吻,

2

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

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

“吉伊的小屋” (@lingnabeierxw), 1,983 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lingnabeierxw.

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.