有在打的带图找我 新手不要呢
Signed 8527

Channel
@nb852701
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
1,649subscribers
+37 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002204429930 |
|---|---|
| Type | Channel |
| Username | @nb852701 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 8 October 2026 |
| On Telegram | t.me/nb852701 |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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 |
|---|---|---|
| 8 Oct 2026, 09:14 | 1,649 | +10 |
| 1 Oct 2026, 22:17 | 1,639 | -2 |
| 16 Sept 2026, 12:20 | 1,641 | +4 |
| 12 Sept 2026, 18:37 | 1,637 | +6 |
| 8 Sept 2026, 19:21 | 1,631 | +8 |
| 3 Sept 2026, 19:00 | 1,623 | +2 |
| 31 Aug 2026, 02:24 | 1,621 | -4 |
| 27 Aug 2026, 17:28 | 1,625 | +9 |
| 24 Aug 2026, 20:06 | 1,616 | +4 |
| 20 Aug 2026, 21:57 | 1,612 | -2 |
| 17 Aug 2026, 14:18 | 1,614 | +2 |
| 14 Aug 2026, 15:18 | 1,612 | +6 |
| 11 Aug 2026, 03:48 | 1,606 | -4 |
| 8 Aug 2026, 12:37 | 1,610 | -2 |
| 7 Aug 2026, 21:17 | 1,612 | no change |
| 7 Aug 2026, 17:30 | 1,612 | first reading |
20 posts held, back to 19 March 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 1 page 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 20 posts for this entry, the most recent from 17 July 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.
42 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 92.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 92.9% | |
| 🤝 | 2 | 4.76% | |
| 🔥 | 1 | 2.38% |
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 17 of the 20 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 42 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 19 March 2026 to 17 July 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.
有在打的带图找我 新手不要呢
Signed 8527
天马 cpa 色粉 带图跳槽的➕1 有质量的来
Signed 8527
收cpa 打的联系我
❤1
Signed 8527
找我合作先符合两点要求,否则没有谈的必要 第一带上渠道数据反馈图,还有上粉视频和卡密北京时间截图 第二 提供近三天内的接单截图➕钱包流水带北京时间视频 能满足以上两点的再详谈
❤3
Signed 8527
发合作结算记录 打粉视频 看到就会回复, 瞎问的一律不回…
Signed 8527
色粉市场没有统一价,它只有合理价你能找到比我贵的,也能找到比我便宜的,但是靠谱是最珍贵的 有些东西是合作共赢 是不离不弃 出粉找我每天200张卡密!包养一手工作室!卡密丝滑!单价高!打款快!事少!假粉勿扰!能验证工作室的来!别问我收什么,你就说你有什么!什么粉都收! 跳 槽 + 1 粉真款稳 高速交流 直接发姿势 多少量 打粉视频 合作记录 联系不上,留言就行 @nb8527
Signed 8527
抖音要码的可以来谈谈~结算稳定
Signed 8527
恢复了 要报单的可以来了
Signed 8527
搞检查啦,不是不给,是没有卡密啊~ 有了再告诉你们
❤1
Signed 8527
今天盘口处理事情,结算延迟了,控量,请大家耐心等待,不好意思
❤2
Signed 8527
不要问我收粉不收粉,收的,价格也不是问题,市面上都差不多,你的粉是真粉,质量也还行就没问题,给我上粉视频,结算记录我就会回复你~我这里超级稳定
❤2
Signed 8527
打粉的不要啰嗦,直接给在打的记录,上粉视频结算记录,价格不是问题~
🤝2❤1
Signed 8527
Showing the 12 most recent of 20 posts we hold for @nb852701. 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.
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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“8527收粉🌸上粉天马云🌸色粉🌸打粉” (@nb852701), 1,649 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/nb852701.
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.