Telegram RegisterThe public register of Telegram
Telegram profile photo for 圣の查档业务及回单

Channel

圣の查档业务及回单

@shennb1314

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

11subscribers

+2 since we began measuring on 9 September 2026

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

Register entry

Telegram ID-1003951687426
TypeChannel
Username@shennb1314
Created8 September 2026measured — dated from the channel’s first post
First recorded14 September 2026
Last confirmed live14 September 2026
Measurements held3
On Telegramt.me/shennb1314

Growth

911109 September 2026 — 9 subscribers11 September 2026 — 11 subscribers14 September 2026 — 11 subscribers9 September 202614 September 2026
3 measurements spanning 4 days, net +2. 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 9–11 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 08:2311no change
11 Sept 2026, 15:0011+2
9 Sept 2026, 20:479first reading

Engagement

16 posts held, back to 8 September 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
4166.7%
avg views ÷ 11 subscribers
Avg views / post
458
9 posts measured
Reaction rate
0.13%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 9 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 13 September 2026
Posts held16 (8 September 202613 September 2026)
Views total4,125
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Sept 2026, 08:23 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
7
Links
1

Lifetime counters from Telegram’s own channel header, read 14 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

2 reactions across 1 post, in 1 kind.

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

Measured over the 16 most recent posts we hold, published 8 September 2026 to 13 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

10 Sept 2026, 15:59 UTC827 viewsread 14 September 2026
Photo

📱抖反来单😀😀无限接 晚上10点前报单隔天回 晚上10点反报单后天回 点击查看更多回单诚信记录 全网反诈无记录 报单 @shenfh666 双向联系 @shenfh666bot

9 Sept 2026, 15:15 UTC659 viewsread 14 September 2026
Photo

📱抖反😀😀无限接诚信回单 业务 @shenfh666 双向在个人简介

9 Sept 2026, 15:09 UTC70 viewsread 14 September 2026
Photo

机主诚信回单 现在报单有福利啦福利不管金额多少都送头 业务联系 @shenfh666

8 Sept 2026, 13:57 UTC785 viewsread 14 September 2026
Photo

支机诚信回单效率诚信第一 支机😀😀送假地址 报单 @shenfh666

8 Sept 2026, 11:11 UTCviews —

圣の查档业务及回单 pinned «🤑本人业务如下🤑 各种平台反手机号 📱快反😀😀 📱抖反😀😀 📱抖反手机号➕实名😀😀📱高概率微反😀😀😀 你只需要提供平台号将会提供给你手机号 ✔️以及码反业务✔️ ❤️支码反无地区😃😀 带地区😀😀 📱微码反😀😀 支付宝提供手机号➕姓名 微信提供姓名 ✔️以及部分查档业务✔️ 机主😀😀 支机😀😀 联通😀😀 假地😀😀 全国头😀😀 以上就是查档业务 有许多并没有写出来 如果你想要其他业务可以询问看看 本人诚信第一 反诈没有任何一条记录不熟不先单 联系 @shenfh666»

8 Sept 2026, 11:11 UTC≈1,540 views2 reactionsread 14 September 2026

🤑本人业务如下🤑 各种平台反手机号 📱快反😀😀 📱抖反😀😀 📱抖反手机号➕实名😀😀📱高概率微反😀😀😀 你只需要提供平台号将会提供给你手机号 ✔️以及码反业务✔️ ❤️支码反无地区😃😀 带地区😀😀 📱微码反😀😀 支付宝提供手机号➕姓名 微信提供姓名 ✔️以及部分查档业务✔️ 机主😀😀 支机😀😀 联通😀😀 假地😀😀 全国头😀😀 以上就是查档业务 有许多并没有写出来 如果你想要其他业务可以询问看看 本人诚信第一 反诈没有任何一条记录不熟不先单 联系 @shenfh666

2

8 Sept 2026, 11:01 UTCviews —

圣の查档业务及回单 pinned «⚠️ Joint Announcement on Channel Compliance and Protection | Jointly Safeguard a Healthy Community Environment Dear Members, To maintain the legal, safe and healthy operation of this Telegram channel 赤の小窝 and protect the legitimate rights and interests of…»

8 Sept 2026, 11:01 UTC71 viewsread 14 September 2026

⚠️ Joint Announcement on Channel Compliance and Protection | Jointly Safeguard a Healthy Community Environment Dear Members, To maintain the legal, safe and healthy operation of this Telegram channel 赤の小窝 and protect the legitimate rights and interests of all users, in response to the recent platform environment dynamics, this channel solemnly issues the following joint announcement on compliance operation and safe

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

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.

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

“圣の查档业务及回单” (@shennb1314), 11 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/shennb1314.

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.