Telegram RegisterThe public register of Telegram

Channel

【七娅】美食素材🍲

@sucai213

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

27,456subscribers

-2,478 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001461208392
TypeChannel
Username@sucai213
Description🌸热爱美食 🌸热爱生活 海外美食,中国美食,素材每日更新,你的关注,是我最大的动力! 商务合作 @kfqiya
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/sucai213

Growth

27,45629,93428,6958 August 2026 — 29,934 subscribers8 August 2026 — 29,934 subscribers9 August 2026 — 29,581 subscribers10 August 2026 — 29,240 subscribers11 August 2026 — 28,947 subscribers11 August 2026 — 28,519 subscribers13 August 2026 — 27,850 subscribers14 August 2026 — 27,456 subscribers8 August 202614 August 2026
8 measurements spanning 6 days, net -2,478. 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 27,084–30,306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 04:4827,456-394
13 Aug 2026, 00:3827,850-669
11 Aug 2026, 22:2328,519-428
11 Aug 2026, 01:0228,947-293
10 Aug 2026, 00:5429,240-341
9 Aug 2026, 02:5229,581-353
8 Aug 2026, 05:0329,934no change
8 Aug 2026, 03:1629,934first reading

Engagement

13 posts held, back to 6 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.752%
avg views ÷ 27,456 subscribers
Avg views / post
206
13 posts measured
Reaction rate
0.893%
reactions ÷ views · ER floor
Posts in window
13
of 13 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 1 of 13 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 11 August 2026
Posts held13 (6 August 202611 August 2026)
Views total2,684
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 15:16 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
66,900
Videos
37,100
Links
5,720

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. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
2s
Average length
2s

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

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

Measured over the 13 most recent posts we hold, published 6 August 2026 to 11 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.

Recent posts

11 Aug 2026, 12:22 UTC423 viewsread 14 August 2026

🙁☺️😚🙂‍↔️☺️😉 😮【亚洲女套图 】 😮 【亚洲男套图 】 😮 😮【欧美女套图 】 😮 【欧美男套图 】 😮 😮【私密女套图 】 😮 【私密女套图 】 😮 😮【海外素材库 】 😮 【美食素材库 】 😮 😮【文案素材库 】 😮 【海外智能AI 】 😮 😮【海外大事件 】 😮 【业务频道 】 😮 😮【证件定制PS 】 😮 【素描彩绘画 】 😮 😮【写人设资料 】 😮 【代开TG会员】 😮 😮【定制表情图标】 😮 【午夜小电影 】😮 😮😥🥺😬🙄😥😮😟😶‍🌫️ 客 服 咨 询😌: @kfqiya 双 向 联 系😌 : @qiyaai_bot 😀😊😊😃🙂😊😊😊😃☺️😳

11 Aug 2026, 12:22 UTC212 viewsread 14 August 2026
Photo

今天下午,我突发奇想,特别想吃玉米🌽。于是,拿起空气炸锅,决定做一份简单又美味的玉米。这种随心而来的小渴望,常常让我觉得生活中的小确幸就在眼前。 我拿出两根新鲜的玉米棒,轻轻擦拭干净,刷上一层橄榄油,撒上盐和黑胡椒。空气中立刻弥漫着香气,调味虽然简单,却充满了期待。我把它们放进空气炸锅,等待着美味的降临。 大约十分钟后,空气炸锅发出了提示音,玉米棒表面微微金黄,散发着诱人的香气。我迫不及待地咬上一口,香甜多汁,酥脆的口感瞬间让人满足,所有的疲惫仿佛都被这份美味驱散。 坐在书房里,我手里捧着热气腾腾的玉米棒,细细品味着它的每一口。这种简单的幸福让我心生温暖,生活中的小快乐,竟能如此打动心灵,带来满满的满足感。 有时我们追求复杂的体验,却忽略了简单的快乐。今天,一根普通的玉米棒让我感受到心灵的宁静和满足。也许,生活的美好就在这些平凡的小事里,值得我们用心去感受。你有没有过类似的瞬间? #玉米 #话题 #日常 #通用

11 Aug 2026, 12:22 UTC112 views1 reactionsread 14 August 2026
Photo

夏天的快乐,是满满一碗水果沙拉给的! #沙拉 #美食 #日常 #分享

1

6 Aug 2026, 11:56 UTC502 viewsread 10 August 2026

🙁☺️😚🙂‍↔️☺️😉 😮【亚洲女套图 】 😮 【亚洲男套图 】 😮 😮【欧美女套图 】 😮 【欧美男套图 】 😮 😮【私密女套图 】 😮 【私密女套图 】 😮 😮【海外素材库 】 😮 【美食素材库 】 😮 😮【文案素材库 】 😮 【海外智能AI 】 😮 😮【海外大事件 】 😮 【业务频道 】 😮 😮【证件定制PS 】 😮 【素描彩绘画 】 😮 😮【写人设资料 】 😮 【代开TG会员】 😮 😮【定制表情图标】 😮 【午夜小电影 】😮 😮😥🥺😬🙄😥😮😟😶‍🌫️ 客 服 咨 询😌: @kfqiya 双 向 联 系😌 : @qiyaai_bot 😀😊😊😃🙂😊😊😊😃☺️😳

6 Aug 2026, 11:54 UTC291 viewsread 10 August 2026
Photo

#做饭 #三文鱼 #晚餐 #意大利面 🍋柠香奶油三文鱼意面

6 Aug 2026, 11:54 UTC200 viewsread 10 August 2026
Photo

今天上班被同事疯狂投喂的一天 一边工作一边吃着同事准备的水果,菠萝、蓝莓还有小樱桃,瞬间感觉下午都变得有精神了 忙碌的工作里,能被这样小小地照顾一下,心情都会变好很多 #水果 #办公室 #日常 #分享 #通用

6 Aug 2026, 11:54 UTC158 viewsread 10 August 2026
Photo

能大口吃苹果是最幸福的事🍎 #水果 #苹果 #日常 #分享 #通用

6 Aug 2026, 11:54 UTC136 viewsread 10 August 2026
Photo

不是没熟 是肌红蛋白 #牛排 #美食 #居家 #日常 #分享

6 Aug 2026, 11:54 UTC122 viewsread 10 August 2026
Photo

有些水果吃完是馋,牛油果吃完是安定 他的口感很有存在感,味道又不会乱跑 是那种坚果油脂香,干干糯糯的特别的丝滑 而且他营养很丰富,你吃完之后胃力很踏实 对身体还没有负担 尤其是忙到没时间好好吃饭的人 家里有几个牛油果吃完真的会很安心 #牛油果 #水果 #通用

Showing the 12 most recent of 13 posts we hold for @sucai213. 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 — 164,938 of 1,340,412entries 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.

Mentions

Named by 11 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

吃瓜中心|热点曝光
@chigua6680 · 239,884
Telegram ranks this channel #27 of 59 here — alongside 58 others — read 11 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“【七娅】美食素材🍲” (@sucai213), 27,456 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sucai213.

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.