Channel
@szbajypd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,475subscribers
+664 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001331851505 |
|---|---|
| Type | Channel |
| Username | @szbajypd |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/szbajypd |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 71% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 00:20 | 4,475 | +77 |
| 14 Sept 2026, 16:02 | 4,398 | +36 |
| 11 Sept 2026, 07:59 | 4,362 | +55 |
| 6 Sept 2026, 18:56 | 4,307 | +50 |
| 2 Sept 2026, 13:28 | 4,257 | +39 |
| 30 Aug 2026, 05:12 | 4,218 | +43 |
| 26 Aug 2026, 18:17 | 4,175 | +46 |
| 23 Aug 2026, 15:46 | 4,129 | +51 |
| 20 Aug 2026, 02:05 | 4,078 | +33 |
| 16 Aug 2026, 18:16 | 4,045 | +57 |
| 13 Aug 2026, 15:46 | 3,988 | +68 |
| 10 Aug 2026, 13:12 | 3,920 | +92 |
| 7 Aug 2026, 13:27 | 3,828 | +17 |
| 6 Aug 2026, 20:05 | 3,811 | first reading |
12 posts held, back to 29 June 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 5 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
69 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 78.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 54 | 78.3% | |
| 👍 | 9 | 13.0% | |
| 🥰 | 4 | 5.80% | |
| 👌 | 2 | 2.90% |
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 12 of the 12 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 69 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 29 June 2026 to 6 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.
感谢大家一年多来的支持 因为我们之前一直都有一个靠谱的口碑 为了保证服务质量和人员质量 后续会建立新人筛选机制 不单单由我们店内管理进行筛选 也让大家进行筛选 新人前期都会放出5-8个半价给大家 希望大家都能帮忙给出客观的报告和评价😁 半价卷的放出和评分规则大家可以后续多关注一下我们的新人内部抽奖群 这个事情在放评价和报告之前或者以后都不会告知新人妹妹 免得伤她的心 大家可以放心写实 之前群组有风控 大家进一下新的 大家加入新群组 旧抽奖群组有风控问题 导致无法创建抽奖 目前只审核有过预约记录的人 https://t.me/szklmnb
抓鸟报告：https://t.me/szklmbg 验证留名：晚霞 验证地区：宝安 抓鸡花费:7 张 颜值身材 ：娇小型满分💯 体验细节 ：本来下午约了客户，结果从十二点一直等到一点半，硬生生被放了鸽子。刚好最近压力挺大，加上进群也挺久了却一直没出击过，当时在路上越想越烦，索性掏出手机查了下定位。发现宝安的最近，几个站就到了，当即决定：果断出击！ 在路上还闹了个乌龙，看错地名提前两个站就下了地铁。外面太阳大得很，路过水果店时索性挑了些西瓜提着，按着遥控指示上了楼。其实门本来是开着的，我却还傻乎乎地去按门铃。 一进门，土豆就迎了上来，递水、换鞋，全套安排得妥妥当当。我当时像个木头一样站在原地，甚至有点结巴地问：“我要干啥？”她忍不住笑了一下，耐心地带我进房间，告诉我在哪挂衣服、怎么去洗澡。 第一次来我是真的两眼一抹黑，冲完凉擦干水躺到床上时，脑子里还在想：“这就直接开始了？”土豆上来就让我把腿张开，我更懵了，问我是要按摩还是直接开…
大家周末快乐😁😁 周末预约比较紧密 大家尽量提前预约啦 吉伊宝宝的体操服近照 无美颜无滤镜 预约 @szjybapm 火爆聊天群 @szklmgp 双向联系 @szjybabot
❤1👍1
抓鸟报告：https://t.me/szklmbg 验证留名：晚霞 验证地区：宝安 抓鸡花费:7 张 颜值身材 ：娇小型满分💯 体验细节 ：本来下午约了客户，结果从十二点一直等到一点半，硬生生被放了鸽子。刚好最近压力挺大，加上进群也挺久了却一直没出击过，当时在路上越想越烦，索性掏出手机查了下定位。发现宝安的最近，几个站就到了，当即决定：果断出击！ 在路上还闹了个乌龙，看错地名提前两个站就下了地铁。外面太阳大得很，路过水果店时索性挑了些西瓜提着，按着遥控指示上了楼。其实门本来是开着的，我却还傻乎乎地去按门铃。 一进门，土豆就迎了上来，递水、换鞋，全套安排得妥妥当当。我当时像个木头一样站在原地，甚至有点结巴地问：“我要干啥？”她忍不住笑了一下，耐心地带我进房间，告诉我在哪挂衣服、怎么去洗澡。 第一次来我是真的两眼一抹黑，冲完凉擦干水躺到床上时，脑子里还在想：“这就直接开始了？”土豆上来就让我把腿张开，我更懵了，问我是要按摩还是直接开…
❤7
小土豆之校服风😁😁😁 宝安营业时间是下午1点-晚上12点 预约 @szjybapm
❤7
发一遍土豆的长报告 土豆性格特别好 情绪价值嘎嘎猛😁😁 预约: @szjybapm
❤3
吉伊艺术照也出炉啦😁😁😁
❤8👍2👌1
抓鸟报告：https://t.me/szklmbg 验证留名：腻腻 验证地区：宝安店 抓鸡花费: 陆佰玖拾捌元 颜值身材 ：白色蕾丝V领常服，齐X超短蕾丝热裤。 体验细节 ：准时到达之后开门就见到嫩嫩的土豆，初见面就很熟络的邻家感觉，领我在客厅换鞋的时候，还被躲在厨房门后的考拉吓了一大跳。然后进房间放东西就知道为什么要在客厅换了因为对比考拉窝来说土豆烹饪室是比较小的。 平时都是躺着的，跟土豆聊完之后发现还可以靠着的方式来FW，于是乎把垫好一次性垫子的枕头放腰，可以坐着更近距离的看着妹妹的脸了，然后就掀起了裙子，脱掉并展示了下烧烧的内裤之后，土豆老师一上油就立马雨后春笋了，被她夸很硬嘿嘿。 开始先是拨筋疏通，有点小反应变软了，土豆还贴心的怕我尴尬安抚我说这个阶段就是有可能会软的，一会就又让你变硬了。期间我们闲聊了很多，讲起了我6月就想来了拖到了现在，土豆给的反应我都觉得太有情绪价值了，还有很可爱的口头禅回复，经常都会说“嗯呢”这样…
❤3
抓鸟报告：https://t.me/szklmbg 验证留名：umi 验证地区：宝安 抓鸡花费:698 颜值身材 ：9.5/10 体验细节 ：今天本来准备和群友一起双排的，可惜时间对不上就只剩我一人了，本来我也想着再等两天去的，可是看到了土豆今天的ootd直接坚定了去的决心（超级可爱！）。一进门就看到小小一只的土豆在迎接，和发的ootd上一样的服装，非常可爱，然后就带我进房间放东西洗澡，还问我要不要丝袜，好贴心，可惜只有黑丝了，白丝更可爱，不过也很玉，然后就开始了，过程中和土豆一直在聊天，土豆非常热情，不会冷场子，手法好到让我的🐣一直在颤抖，土豆还说太久没弄生疏了，完全没有，玩到一半土豆问我要不要足，果断点头，黑丝的质感非常好，很柔很滑，土豆的脚小小的，才34、35码，很嫩很软，足技没得说，太会了，左右扭来扭去直接给我爽的受不了了，玩了会儿又把黑丝开洞，直接玩上非常期待的丝袜包🐣了，土豆嫩嫩的小脚配合上略微粗糙的丝袜，足的体验感…
❤6👍2
小土豆今天的护士服ootd😍😍 预约: @szjybapm
❤5👍2
更新一篇考拉轻度S的体验😍😍 预约联系: @szjybapm 火爆聊天群 @szklmgp 快速搜索报告 @szklmbg
👍2❤1🥰1
考拉今天的ootd 美爆了😍😍😍 预约 @szjybapm
❤13🥰3👌1
Showing the 12 most recent of 12 posts we hold for @szbajypd. 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.
Named by 17 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳宝安吉伊抓龙筋丝足SM” (@szbajypd), 4,475 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/szbajypd.
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.