Channel
@SZJPbg0000
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,776subscribers
-14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002658212690 |
|---|---|
| Type | Channel |
| Username | @SZJPbg0000 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/SZJPbg0000 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:27 | 1,776 | -10 |
| 10 Aug 2026, 08:11 | 1,786 | -7 |
| 7 Aug 2026, 15:41 | 1,793 | +3 |
| 6 Aug 2026, 20:05 | 1,790 | first reading |
23 posts held, back to 28 July 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 2 pagesof Telegram’s post history, 20 posts per page.
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 23 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 23 (28 July 2026 – 7 August 2026) |
| Views total | 4,989 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:30 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.
#报告模版(长按右键复制) <精品修车报告> 验证留名： 冬天 上课时间： 8.7 老师花名： #小团团 联系方式： @abcxal 位置坐标： #福田 修车水费： 14p 颜值身材： 照片一致 服务内容： 课表 出击体验：这两天过来出差，闲暇时间刷TG，榜上看中了小团团老师，于是果断出击，联系好时间就驾车前往。见面第一眼很喜欢，气质很好 颜值很高，清纯高级的感觉。闲聊片刻交了水费就火急火燎去洗澡。洗完来到床上老师爬上来先舔我咪咪，一边舔一边手握住小弟弟套弄，弄得我很快就硬了。老师一对天然🐻，又软又弹，我两手抓着爱不释手，不停揉捏把玩，乳头也硬得明显。接着老师小嘴一路往下亲，一手扶着小弟弟，张开嘴时浅时深吞吐起来，卖力得很，舌头一直绕着龟头转，含得湿热舒服，不叫停就一直口，热乎乎滑溜溜的，爽得我直喘。硬得实在受不了，赶紧戴套女上位。坐下来小穴包裹感很足，热紧热紧的，一边骑我一边继续抓着她一对🐻揉。骑了一会儿换传教士压着干，还是那…
#报告模版(长按右键复制) <精品修车报告> 验证留名： #乌索普 上课时间： 7月31 老师花名： #夏朵朵 联系方式：@xiaduoduo123 位置坐标： #深圳 #南山 修车水费：900半价 颜值身材：人照一致身材好 服务内容：课表上都有 出击体验：课室位置方便好找，课室大窗户夜景很棒。身材凹凸有致，皮肤好又白又滑，摸起来很舒服，态度好，口活好，服务意识很到位，骚的不行，窗帘不拉，站在窗边看着夜景做，体验很独特，做起来舒服。 优点缺点：服务不错 值得去 推荐程度：⭐️⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/强烈推荐，必返食） 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课记录 📜 个人感受仅供参考 交流群 ❤️ 推荐榜 ❤️ 报告
#报告模版(长按右键复制) <精品修车报告> 验证留名： #峡谷第一深情 上课时间： 08.06 老师花名： #舒瑶 联系方式： @linlinai6968 位置坐标： #深圳 #坂田 修车水费： 900p 颜值身材： 大长腿🦵 服务内容： 69 🐍 出击体验： 看到小姐姐频道描述都挺好的，就决定过去试试。过去没等一分钟，准时就上楼了。见面看到小姐姐确实嫩妹妹，颜值姣好，身高体廋。刚开始摸一摸，亲了起来，慢慢的她也来了感觉，会伸手挽着头，呼吸急促。后续换了两个姿势，舒瑶都夹得很紧，小弟弟感觉全方位照顾，顶到底部还有反弹感觉。舒瑶声音也很好听，年轻感觉让人都年轻了，今天开心了 比照片好看，视频那样的感觉，非常ok 优点缺点： 嫩 白 紧 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/强烈推荐，必返食） 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课…
报告模版(长按右键复制) <精品修车报告> 验证留名： #李亚西 上课时间： 2026-08-07 老师花名： #猫奴 联系方式： @weiiii3333 位置坐标： #深圳 #龙华 修车水费： 899半价 颜值身材： 7分，身材可以 服务内容： 陪浴 调情 洗吹做 出击体验： 用半价券出击，猫奴老师科室环境干净整洁，一进去就感觉放松。老师真人颜值不算高，但是比较可爱，胸适中，摸着又软又弹，视觉和手感都不错。 老师态度特别好，心善有交流，年轻腼腆话不多，服务陪洗全程配合，刚入行不久，动作技术略显生疏，前戏调情纯感，整个过程配合度满意。出击完一起抽了根事后烟。 优点缺点： 嫩妹，刚做没啥服务 推荐程度：⭐️⭐️⭐️ 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课记录 📜 个人感受仅供参考 交流群 ❤️ 推荐榜 ❤️ 报告
#报告模版(长按右键复制) <精品修车报告> 验证留名： #刘柳 上课时间： 8.6号 老师花名： #桃子 联系方式： @lgjzxm2 位置坐标： #深圳 #龙岗 修车水费： 700p 颜值身材： 年轻很嫩 漂亮比照片好看 服务内容： 洗吹做69舌吻课表都有 出击体验： 看到新来18年轻妹妹 果断问了位置驱车赶到课室 遥控上楼 房间温馨 一见面老师穿着高跟鞋 身材比例颜值比照片好看多了 老师说不会拍照 随后老师帮忙拿拖鞋递水喝 交了水费就一起洗澡 在床上我先来舔的老师。不会不会催人 让人吃到饱 下面还很软粉的 毛少 随后我躺下老师口活有待提升 随后带上雨伞☔️后入 随后沙发 姿势都可以 屁股蜜桃臀 后入很舒服 配合度高不催 很紧 优点缺点： 除了口活有待提升其他都很完美 属于很顶的老师 毕竟刚开始。也算理解了 下次还会来 很舒服 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/…
#报告模版(长按右键复制) <精品修车报告> 验证留名： #派大星 上课时间： 8月6日 老师花名： #丹丹 联系方式： @dandaner 位置坐标： #深圳 #宝安 修车水费： 700p 颜值身材： 9分 服务内容： 课表都有 出击体验： 运气不错抽中频道新来老师的券，是兼职上门的老师，跟老师约了时间，老师打车过来非常守时，不用站街等的感觉非常好！第一眼看到老师是气质型打扮，人照合一非常满意！老师不抽烟，嘴里无烟味，聊了一下，老师性格开朗爱笑，服务课表都有，陪洗，kiss，69，特别有女友感，一点都不装，适合喜欢嫩妹+女友感的朋友，跟老师缠绵完一起洗洗聊聊天，送别老师，剩下老师的气味和美好回忆，下次还会再约丹丹老师！ 优点缺点： 优点：自聊，照片人照合一，性格好，课表一样不少，很有耐心愿意听指挥，服务+嫩妹型，非常满意 缺点：老师住宿舍，只接受上门，但对我来说也是优点 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/差…
#报告模版(长按右键复制) <精品修车报告> 验证留名： #干饭 上课时间： 8月6日 老师花名： #果果 联系方式： @Guosz2008 位置坐标： #深圳 #龙华 修车水费： 700半价 颜值身材： 8 服务内容： 帮洗，口，做 出击体验： 妹子确实一个嫩妹，身材娇小，会的不多，刚进去就让我脱衣服，然后马上自己也脱光了，然后去浴室帮洗，洗完出来聊了几句就到床上，就帮口，口了一分钟就马上开始做先是女上，然后换成传教士，不知道是不是没有前戏的原因123就交货了，然后让我自己去洗，我洗完出来她已经穿好衣服了，就躺在沙发上玩手机，体验一般，如同快餐。 优点缺点： 嫩妹，白，没太多服务 推荐程度：⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/强烈推荐，必返食） 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课记录 📜 个人感受仅供参考 交流群 ❤️ 推荐榜 ❤️ 报告
#报告模版(长按右键复制) <精品修车报告> 验证留名： #拱手相让 上课时间： 8月5日 老师花名： #晓晓 联系方式： @xiao168999 位置坐标： #深圳 #宝安 修车水费： 499元 颜值身材： 御姐 服务内容： 口爆 出击体验： 听狼友们说：宝安晓晓老师服务好，口活好，花样多会玩，心血来潮，马上问朋友要了联系方式，预约晓晓老师下午3点时间。出发路程40分钟，到了位置指引上楼，开门见到老师，本人比频道里照片视频漂亮多了，聊了一会儿，交了水费，老师放水给我洗澡搓背，洗完回到床上，老师床上用的全部是一次性服务用品，干净卫生。躺在床上开始服务，全身按摩放松，莞式调情，舌尖漫游，毒龙69，课表上该有的都有，详细我就不用说了，服务很到位。最突出的就是调情和口活了，完全没有齿感，一下子没有控制住被秒射，爆在老师嘴里，这次出击很棒，下次还会出击，值得推荐 优点缺点： 口活好 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/…
#报告模版(长按右键复制) <精品修车报告> 验证留名： #🐯 上课时间： 08.05 老师花名： #舒瑶 联系方式： @linlinai6968 位置坐标： #深圳 #坂田 修车水费： 900p 颜值身材： 大长腿🦵 服务内容： 69 🐍 出击体验： 队长说的对！嫩妹要趁早！果断预约了舒瑶，进门看到一双大长腿出现，我就知道，来对了！仔细观察了一下，妹妹是个高瘦嫩妹，颜值也不错，尤其是那双腿，比命还长，就是比较害羞，抓紧给了水费洗澡，妹妹洗的很认真，然后就上楼。一躺床上，妹子就跟一只鸵鸟一样，头直接塞进我的怀抱。开始大蟒蛇起步，随便🐍，然后挑逗一下妹妹，妹妹很怕痒，敏感，接着就开始口，毕竟是嫩妹，口活比较轻柔，但是很认真。老二硬的受不了了，直接让妹妹带上🌂，开始女上，没想到还有惊喜！弟弟进去了之后，妹妹开始大方了起来，我沉醉在一声声老公里面不能自拨，后面直接传教士，一边蛇一边听妹妹的呢喃声，123直接秒了。很不错的体验，…
<精品修车报告> 验证留名： 铭铭 上课时间： 8月3日 老师花名： #晓晓 联系方式： @xiao168999 位置坐标： #深圳 #宝安 修车水费： 499元 颜值身材： 御姐 服务内容： 口爆 出击体验： 必须上一波反馈，晓晓真的很极品，约了工作室，到了给我指引上楼，见面非常热情，本来想着又是假图什么的，她频道的视频照片就是她自己本人，身材也非常奈斯，皮肤白，本人属于丰满御姐型，穿着打扮相当性感，服务期间更是情绪价值拉满，毒龙，69，各种花式调情，相当不错，口活可以说是天花板，特别骚气，吸力感非常足，服务调情更是应有尽有，比那种什么也不会的小妹妹更有性价比啊，必须好评！ 优点缺点： 口活好 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/强烈推荐，必返食） 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课记录 📜 个人感受仅供参考 交流群 ❤️ 推荐榜…
#报告模版(长按右键复制) <精品修车报告> 验证留名 123 上课时间： 8.2 老师花名：艾喜悅-琪琪老师 联系方式： @nskf168 @siu_i4uBB 位置坐标： #深圳 #福田 修车水费： 1400 颜值身材： 10 服务内容：10 出击体验：琪琪老师手法专业娴熟，力度可以随时调节，肩颈僵硬的部位按完轻松了很多。环境安静整洁，私密性很好，全程没有多余推销，体验感特别舒服。做完之后浑身疲惫一扫而空，整个人都放松下来了。性价比很高，服务细致贴心，下次有需要还会再来，非常推荐。 优点缺点：10 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/差，三星/正常，四星/推荐，五星/强烈推荐，必返食） 投稿联系： @jpxcbhzBot 📜 报告务必真实反馈 📜 必须提供约课记录 📜 个人感受仅供参考 交流群 ❤️ 推荐榜 ❤️ 报告
#报告模版(长按右键复制) <精品修车报告> 验证留名： #阿么 上课时间： 8月1日 老师花名： #晓晓 联系方式： @xiao168999 位置坐标： #深圳 #宝安 修车水费： 1388元 颜值身材： 都非常棒 服务内容： 口爆3飞 出击体验： 朋友推荐，听说晓晓老师这里几个闺蜜一起，可以安排三飞，问朋友要了晓晓老师的联系方式，果断提前预约下午时间，过来体验一下三飞闺蜜团，来到位置，路线图指引上楼，开门进来，看到老师身材好满意，说话好温柔，聊了一会，交了水费，我们俩去洗澡，洗完出来在床上，闺蜜也进来了，身材都差不多，小跟晓晓🐍起来，摸着大🐻，又大又软。过瘾，闺蜜在后面从上往下轻轻舔，整个人酸酸麻麻，好难顶，晓晓老师深喉口的时候我射了，擦干净后继续服务，开始调情，老二又翅起来了，我吃鲍鱼爽得一波，独🐉，69式配合的太好了，最后在姐妹的猛攻下交完作业， 优点缺点： 配合好 推荐程度：⭐️⭐️⭐️⭐️⭐️（一星/很差，二星/…
Showing the 12 most recent of 23 posts we hold for @SZJPbg0000. 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 — 96,033 of 1,478,351entries 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.
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.
Named by 5 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@SZJPbg0000 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“深圳精品修车团报告4.0” (@SZJPbg0000), 1,776 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/SZJPbg0000.
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.