Telegram RegisterThe public register of Telegram
Telegram profile photo for 福田琳琳

Channel

福田琳琳

@linszlin

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

113subscribers

+52 since we began measuring on 20 October 2026

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

Register entry

Telegram ID-1004329169960
TypeChannel
Username@linszlin
CreatedBetween 1 June 2026 and 7 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 October 2026
Last confirmed live11 November 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/linszlin

Topic

Local community — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 51% 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 the other topics.

Growth

611138720 October 2026 — 61 subscribers21 October 2026 — 66 subscribers27 October 2026 — 81 subscribers2 November 2026 — 100 subscribers11 November 2026 — 113 subscribers20 October 202611 November 2026
5 measurements spanning 22 days, net +52. 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 53–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Nov 2026, 10:48113+13
2 Nov 2026, 17:00100+19
27 Oct 2026, 12:3081+15
21 Oct 2026, 11:0966+5
20 Oct 2026, 17:2261first reading

Engagement

18 posts held, back to 7 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
74.3%
avg views ÷ 113 subscribers
Avg views / post
84.0
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
of 18 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 20 October 2026
Posts held18 (7 October 2026 – 20 October 2026)
Views total588
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Oct 2026, 17: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
18s
Average length
9s

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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 18 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 7 October 2026 to 20 October 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 7 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).

20 Oct 2026, 12:59 UTC38 viewsread 20 October 2026

深圳茶餐厅 🍵 本群倡导言论自由,欢迎诸位踊跃交流,并设有丰富福利活动 🎉(红包🧧、💰现金加抽奖)只要你来我们的缘分就开启啦… 最重要的是:老板娘超有趣的🤫 茶餐厅:https://telegram.me/Sz_cct 取餐区:https://t.me/Sz_qcq 老板娘:@CCTgly 双向联系:@LBNZS_bot 🤝

20 Oct 2026, 10:05 UTC48 viewsread 20 October 2026

🎉 抽奖活动:福田 琳琳 @ilinlinai 抽奖活动 📝 说明: ❗️点击👉 @szxglyhglBot 进入机器人查阅老师榜。 t.me/szxglyhglBot?start=-1002640036076 没有群主只有玩家,纯交流纯分享群,分享优质老师,发掘优秀新人。 🎁 奖品: - p100 x 3 - pp200 x 5 ⏰ 开奖时间(北京时间): 2026年10月23日 18:00:00 ⏳ 距离开奖还有 71 小时 54 分 📋 参与条件: 深圳香港老友会共享资源(2026) 深圳香港老友会抽奖优惠 福田琳琳

19 Oct 2026, 08:54 UTC154 viewsread 20 October 2026

#琳琳 已在「老友会」验证上榜 👇👇👇👇👇👇👇👇 查看 距离 营业时间 : t.me/szxglyhOneBot?startapp=td_972910377 👆👆👆👆👆👆👆👆 打造纯净生态,不负信赖与热爱。 加群/频道: t.me/szxglyhOneBot?startapp=glist 加群机器人: @szxglyhglBot

10 Oct 2026, 09:38 UTC284 views1 reactionsread 20 October 2026

茶楼报告( https://t.me/szclzBG ) 【位置艺名】:新人琳琳 【联系方式】:@ilinlinai 【喝茶留名】:颜值 【喝茶时间】:10/10 【喝茶价格】:700 【芳龄身高】:168 【罩杯手感】:F 【服务内容】:课表 【优点缺点】:水多 【体验细节】:公寓安全进门容易,妹妹热情招待递水,妹妹主动提出陪浴,洗刷结束开始ab面服务,来到B面,我果断让妹妹躺好我来服侍妹妹,妹妹敏感反馈足,口活非常厉害,会深喉,随即带套插入,又紧又烫,妹妹做爱反馈感拉满,动情处会紧紧抱着不松手,用手一摸已经水漫金山,中间体力不支导致疲软,妹妹很有耐心等待二弟二次唤醒,换套后传教顺利出货,传教时妹妹屁股会主动翘起来迎和,满分!!! 【温馨提醒】:报告仅供参考,请理性选择,切勿对号入座。 深圳茶楼报告管理员 @Sanlimi_bot

❤1

Showing the 12 most recent of 18 posts we hold for @linszlin. 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.

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

“福田琳琳” (@linszlin), 113 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/linszlin.

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.