都叫发幼师资格证现在给你们发啦
❤2👍1
Signed 福田 幼师恋恋

Channel
@lianliana99
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,925subscribers
+583 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003646816041 |
|---|---|
| Type | Channel |
| Username | @lianliana99 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/lianliana99 |
Giveaways & airdrops — 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 16 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 |
|---|---|---|
| 18 Sept 2026, 03:41 | 1,925 | +15 |
| 14 Sept 2026, 06:57 | 1,910 | +32 |
| 10 Sept 2026, 13:36 | 1,878 | +76 |
| 5 Sept 2026, 13:16 | 1,802 | +93 |
| 1 Sept 2026, 10:35 | 1,709 | +32 |
| 29 Aug 2026, 06:16 | 1,677 | +80 |
| 26 Aug 2026, 07:54 | 1,597 | +11 |
| 23 Aug 2026, 05:29 | 1,586 | +19 |
| 20 Aug 2026, 01:32 | 1,567 | +18 |
| 17 Aug 2026, 11:17 | 1,549 | +33 |
| 14 Aug 2026, 05:46 | 1,516 | +110 |
| 10 Aug 2026, 14:45 | 1,406 | +52 |
| 7 Aug 2026, 22:58 | 1,354 | +12 |
| 7 Aug 2026, 22:23 | 1,342 | no change |
| 7 Aug 2026, 12:50 | 1,342 | first reading |
15 posts held, back to 17 July 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 15 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
32 reactions across 12 posts, in 5 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 50.0% | |
| 👍 | 9 | 28.1% | |
| 🔥 | 5 | 15.6% | |
| 👏 | 1 | 3.13% | |
| 🥰 | 1 | 3.13% |
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 12 of the 15 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 17 July 2026 to 7 August 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.
都叫发幼师资格证现在给你们发啦
❤2👍1
Signed 福田 幼师恋恋
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178574830829 🎰 福田区幼师嫩妹恋恋上榜福利抽奖 @lianlian168 ⚠️ 抽奖说明: 当前抽奖说明:禁止恶意水群。 禁止刷屏。 禁止军团参与抽奖。 禁止不写报告。 中奖者多次无故不去,取消所有资格,并清退出群,不去就不要参与抽奖。 中奖不去的,不要参与,没去直接踢出群 💁 参与情况:76达标 / 103报名 🔋 人品加成:23票 ⚡️× 9 🎅 联系领奖:@lianlian168 1. 小丑开始 奖品:1p五折优惠劵 2. 77 Alex 奖品:66口令红包 祝大家心想事成好运连连!
Signed LotteryBest Bot
宝宝们可以预约啦
Signed 福田 幼师恋恋
宝宝们今天起来有点晚了,现在开课要过来可以嘀嘀我❤️❤️❤️❤️❤️❤️这是我的出击报告https://t.me/lianlian89
❤1👍1
Signed 福田 幼师恋恋
🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H178575917154 🎰 ED邀约幼师恋恋给粉丝送优惠 ⚠️ 抽奖说明: 1: 奖品为p 或者 pp 任选。 2:中奖者原则上不允许转让。 3:中奖的朋友5天内兑奖,过期作废。 4:兑奖的朋友要在「一个ED的旅行日记」频道中,“恋恋”这一篇日记的评论区留下你的评价。 5:最终解释权归老师所有。 💁 参与人数:135人 🎅 联系领奖:@lianlian168 1. DDD p 奖品:p-200/pp-300 2. Robin Jame... 奖品:p-200/pp-300 3. Dup 奖品:p-200/pp-300 祝大家心想事成好运连连!
Signed LotteryBest Bot
开始预约啦宝宝们
❤1👍1
Signed 福田 幼师恋恋
宝宝们抓紧预约啦头课😘😘我的出击报告https://t.me/lianlian89
❤2👍1🥰1
Signed 福田 幼师恋恋
宝子们可以预约下午课了😘😘我的出击报告https://t.me/lianlian89
❤2👍1👏1🔥1
Signed 福田 幼师恋恋
开始预约上课啦宝宝们
❤1
Signed 福田 幼师恋恋
宝子们现在有空可以预约😍😍我的出击报告https://t.me/lianlian89
❤1👍1🔥1
Signed 福田 幼师恋恋
起床啦宝宝们开始预约啦
❤1
Signed 福田 幼师恋恋
起床床啦宝子们可以预约下午课啦我的出击报告https://t.me/lianlian89
❤2👍1🔥1
Signed 福田 幼师恋恋
Showing the 12 most recent of 15 posts we hold for @lianliana99. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 4 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“福田幼师恋恋” (@lianliana99), 1,925 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/lianliana99.
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.