Telegram RegisterThe public register of Telegram
Telegram profile photo for 海外素材库【SuCai】

Channel

海外素材库【SuCai】

@ZeppTp1

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

27,395subscribers

-2,545 since we began measuring on 17 August 2026

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

Register entry

Telegram ID-1001442848430
TypeChannel
Username@ZeppTp1
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live5 September 2026
Measurements held18
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/ZeppTp1

Growth

27,39529,94028,667.517 August 2026 — 29,940 subscribers18 August 2026 — 29,822 subscribers19 August 2026 — 29,656 subscribers20 August 2026 — 29,409 subscribers21 August 2026 — 29,381 subscribers23 August 2026 — 29,347 subscribers24 August 2026 — 29,319 subscribers25 August 2026 — 29,237 subscribers26 August 2026 — 29,158 subscribers27 August 2026 — 29,133 subscribers28 August 2026 — 29,042 subscribers29 August 2026 — 28,628 subscribers30 August 2026 — 28,345 subscribers31 August 2026 — 28,147 subscribers1 September 2026 — 28,010 subscribers2 September 2026 — 27,698 subscribers3 September 2026 — 27,550 subscribers5 September 2026 — 27,395 subscribers17 August 20265 September 2026
18 measurements spanning 19 days, net -2,545. 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,013–30,322 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 12:2127,395-155
3 Sept 2026, 16:3727,550-148
2 Sept 2026, 10:5527,698-312
1 Sept 2026, 08:1528,010-137
31 Aug 2026, 10:3428,147-198
30 Aug 2026, 12:1728,345-283
29 Aug 2026, 15:2728,628-414
28 Aug 2026, 14:2429,042-91
27 Aug 2026, 11:3729,133-25
26 Aug 2026, 14:4529,158-79
25 Aug 2026, 17:0829,237-82
24 Aug 2026, 15:2829,319-28
23 Aug 2026, 01:0429,347-34
21 Aug 2026, 14:1629,381-28
20 Aug 2026, 17:0329,409-247
19 Aug 2026, 16:2729,656-166
18 Aug 2026, 14:0329,822-118
17 Aug 2026, 21:1629,940first reading

Engagement

27 posts held, back to 16 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 34 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.066%
avg views ÷ 27,395 subscribers
Avg views / post
18.1
27 posts measured
Reaction rate
1.61%
reactions ÷ views · ER floor
Posts in window
27
of 27 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 27 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 4 September 2026
Posts held27 (16 August 20264 September 2026)
Views total489
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Sept 2026, 12:34 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
22s
Average length
3s

Measured directly from 7 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 27 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 27 most recent posts we hold, published 16 August 2026 to 4 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

4 Sept 2026, 08:59 UTC3 viewsread 4 September 2026
Video

#澳大利亚 #墨尔本 #🇦🇺墨尔本Chadstone|Chanel 26B #奢侈品

2 Sept 2026, 09:34 UTC12 viewsread 3 September 2026

中文频道导航中心 海外素材:@ZeppTp1 搞笑吃瓜:@ZeppTp2 新闻曝光:@ZeppTp3 影视大全:@ZeppTp4 深情文案:@ZeppTp5 麻豆传媒:@ZePPTp6

2 Sept 2026, 09:34 UTC12 viewsread 3 September 2026
Video

#伦敦 #伦敦聚会 我愿意把这个forbidden nights show加入朋友的礼物生日清单! 不管是闺蜜聚会,hen party,都是一晚很特别的体验。 现场大概有5个bride to be,每个人都盛装打扮,那种好好为一个场合盛装出席,纪念姐妹的重要纪念日的感觉真的很棒。上台的姐妹们都是朋友们给他们买了stage access. *P.S. 虽然给姐妹准备惊喜很好,但还是建议提前问好她们的尺度! 关于价格和座位的选择 💎 Premium Seats|60pp 离舞台最近的 Cabaret 桌位,包含一小瓶 200ml bubbly。想近距离感受现场氛围,可以直接冲这个。 🥂 Cabaret Seats|45pp 同样是桌位,就在 Premium 后方,整体视野和氛围都不错。 🎭 Stall Seats|35pp 剧院式座位,在稍高的位置,性价比比较高。 💃 Standard Entry|25pp 站席,在

2 Sept 2026, 09:34 UTC3 viewsread 3 September 2026
Photo

#德国 #慕尼黑 #🇩🇪慕尼黑皇家啤酒屋,来了就别想清醒着走

31 Aug 2026, 17:15 UTC17 viewsread 2 September 2026

中文频道导航中心 海外素材:@ZeppTp1 搞笑吃瓜:@ZeppTp2 新闻曝光:@ZeppTp3 影视大全:@ZeppTp4 深情文案:@ZeppTp5 麻豆传媒:@ZePPTp6

27 Aug 2026, 13:18 UTC23 viewsread 31 August 2026

中文频道导航中心 海外素材:@ZeppTp1 搞笑吃瓜:@ZeppTp2 新闻曝光:@ZeppTp3 影视大全:@ZeppTp4 深情文案:@ZeppTp5 麻豆传媒:@ZePPTp6

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

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

“海外素材库【SuCai】” (@ZeppTp1), 27,395 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/ZeppTp1.

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.