Telegram RegisterThe public register of Telegram
Telegram profile photo for 重生之招车队跑分做码接

Channel

重生之招车队跑分做码接

@shedi8888

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry

57subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002972467961
TypeChannel
Username@shedi8888
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/shedi8888

Growth

505954.57 August 2026 — 50 subscribers10 August 2026 — 50 subscribers14 August 2026 — 57 subscribers22 August 2026 — 59 subscribers29 August 2026 — 57 subscribers577 August 202629 August 2026
5 measurements spanning 22 days, net +7. 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 49–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 12:5257-2
22 Aug 2026, 04:1559+2
14 Aug 2026, 22:0457+7
10 Aug 2026, 11:4650no change
7 Aug 2026, 18:4750first reading

Engagement

7 posts held, back to 29 March 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
100.0%
avg views ÷ 57 subscribers
Avg views / post
57.0
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 7 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 8 August 2026
Posts held7 (29 March 20268 August 2026)
Views total228
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 11:46 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
59s
Average length
59s

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

3 reactions across 1 post, in 1 kind.

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

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

8 Aug 2026, 13:08 UTC62 viewsread 10 August 2026

速来车队,散户,一个码都可以打,微信 支付宝 个人码 融合码 经营码都可以 量大料子柔,稳定运营两年多下面车队没有出事儿的 汇率在高打几百 1-2 千没料了赚到你兜里面的钱也有限,来我这边只要码子能进钱,通通拉满! 让辛苦找码的兄弟们单码利润拉到最高!!

8 Aug 2026, 13:07 UTC62 viewsread 10 August 2026

😀😃😀😃😄😀😃😀 👍飞机最稳项目!目前0司法! 😎😎😎 📱📱📱 你给我微信/支付宝收款码,我给你打钱~ 常规色料,保无三黑!0️⃣风险! 常规色料, 保无三黑!0️⃣风险! ⚪大量要 😀微信个人 ,微信经营, 微信收款单 微信群 微信加好友👍 信经营,微信秒打 🟢大量招收😂😂支付宝个人,支付宝经营 ⚪每天100-200万的量,主打量大,单码轻松过万,主打料子柔,打得起量。只要你码子丝滑,一分钟好几笔,查账都查到你手软。 🟢招收京东拉代付码车队,汇率置顶 招收京东拉代付码车队,汇率置顶 京东不懂的不要来,带码来上车 📱📱📱📱📱📱📱📱 😎😎😎😎😎😎😎😎😎 秒打不罚站来就打!日量200w

9 Jul 2026, 16:41 UTC259 views3 reactionsread 10 August 2026

空降直盘招卡接回u车队 带维护😂😂全年24h无休假 📱📱📱📱📱📱📱📱📱 📱:各种银行卡 储蓄卡 取现卡 信用卡 平台卡 贷款卡 扶贫卡 医保卡 定额卡 实效卡等 不限制任何卡 是卡就可以 银行卡信用卡汇率如下💳 💳5000内汇率13 💳5000-10000汇率14 💳10000+汇率14.5 💳20000-30000 汇率15 💳30000-100000 汇率16 💳单笔10w+ 汇率17起 大盘长期招任何卡车 卡多的卡可私聊群内管理议价📱📱📱📱 长期招收私户/公户/专卡/POS专卡/取现卡/冲锋卡🏳️‍🌈🏳️‍🌈🏳️‍🌈 💳本群做单流程 第一步:向本群置顶地址转U,发业务员转u截图,业务员公群报备 第二步:提供接款账户的信息,等待接款 第三步:我方给你打款,确认到账后,按实际接单金额扣除U 🇭🇰🇭🇰🇭🇰 🇭🇰🇭🇰🇭🇰 🇭🇰🇭🇰🇭🇰 🇭🇰🇭🇰🇭🇰 📱📱📱📱📱📱📱📱📱📱📱📱 😘😘:一切业务认准群内管理ID 谨防被骗

3

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

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

“重生之招车队跑分做码接” (@shedi8888), 57 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/shedi8888.

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.