Telegram RegisterThe public register of Telegram
Telegram profile photo for 面包的_卖号小屋

Channel

面包的_卖号小屋

@mianbaowu

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

398subscribers

+220 since we began measuring on 25 September 2026

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

Register entry

Telegram ID-1004339885505
TypeChannel
Username@mianbaowu
CreatedBetween 1 June 2026 and 15 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 September 2026
Last confirmed live12 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/mianbaowu

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 52% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@mianbaowu/13 · this entry18 Sept 2026, 02:59 UTC@mbpdgjx/3218 Sept 2026, 12:16 UTC1.009.3 hours
@mianbaowu/14 · this entry18 Sept 2026, 04:22 UTC@mbpdgjx/3318 Sept 2026, 12:16 UTC1.007.9 hours
@mianbaowu/15 · this entry18 Sept 2026, 07:38 UTC@mbpdgjx/3418 Sept 2026, 12:16 UTC1.004.6 hours
@mianbaowu/23 · this entry20 Sept 2026, 07:37 UTC@mbpdgjx/4420 Sept 2026, 07:38 UTC1.00under a minute
@mianbaowu/24 · this entry21 Sept 2026, 11:52 UTC@mbpdgjx/4521 Sept 2026, 11:52 UTC1.00under a minute
@mianbaowu/25 · this entry21 Sept 2026, 18:59 UTC@mbpdgjx/4621 Sept 2026, 18:59 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@mbpdgjx11 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (10–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 15 September 2026 to 25 September 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @mianbaowu — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

178463320.525 September 2026 — 178 subscribers3 October 2026 — 352 subscribers13 October 2026 — 312 subscribers20 October 2026 — 294 subscribers27 October 2026 — 463 subscribers4 November 2026 — 431 subscribers12 November 2026 — 398 subscribers39825 September 202612 November 2026
7 measurements spanning 49 days, net +220. 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 135–506 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 23:20398-33
4 Nov 2026, 00:49431-32
27 Oct 2026, 23:29463+169
20 Oct 2026, 09:36294-18
13 Oct 2026, 15:37312-40
3 Oct 2026, 13:37352+174
25 Sept 2026, 04:22178first reading

Engagement

20 posts held, back to 15 September 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 25 September 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 2 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 1 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 15 September 2026 to 25 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

25 Sept 2026, 03:00 UTC34 views1 reactionsread 25 September 2026
Photo

🎉 联邦~微凉赞助兔兔.面包铺红包抽奖㊗️联邦兄弟们中秋国庆节快乐 🎁 奖品清单 • 118元🧧红包 × 1 • 88元🧧红包 × 2 • 66元🧧红包 × 3 📢 参与条件 • 加入 广州佛山联邦出击群(重生版) • 加入 面包铺 • 加入 面包的_卖号小屋 • 加入 记录搬砖出击生活 • 加入 麻辣🐰头 • 加入 广州佛山邦女郎动态榜 • 加入 广州佛山联邦老师榜 • 加入 广州佛山商家榜 • 加入 广州佛山联邦抽奖榜 • 需消耗奔周能量:10 • 参加抽奖后需在 广州佛山联邦出击群(重生版) 内发言10次 └ 群内发送“抽奖进度”查看完成度(每日限5次) ⌛ 开奖时间 • 2026-10-01 11:00:00 📜 抽奖说明 兔兔🐰: t.me/Gzffol/43895 面包铺🐶: t.me/hzwddp8888/145 1,本活动由微凉赞助,感谢微凉和面包铺.兔兔老师。 2,中奖者请24小时内联系 @Eve…

❤1

23 Sept 2026, 10:00 UTC68 viewsread 25 September 2026
Photo

✈️ 关于登录过程中 跳邮箱 / sms fee 问题 ,一些补充 我就用我这边出去的号在登录时候出现的情况单独作出一个讲解 🕜 1️⃣ 先从设备方面来看📱 鸿蒙系统和OPPO出现的几率是非常大的 基本上都会有 鸿蒙的话出现了就只能用带会员的号(除了会捣鼓可以安装第三方来登录) 鸿蒙之外的都可以正常安装第三方来登录(我们会给推荐的)这是最经济的方式💡 不额外花钱 ⚠️ 除此之外 有的人第一个手机登录出现了 用其他手机却可以正常登录 这个可以自行尝试 2️⃣ 然后是IP方面 🌎 大多数用户可能对这个不太懂 用的梯子都默认了香港的 ❗️香港ip非常容易出现smsfee 甚至换绑都无法正常换绑 ⚠️ 尝试切换其他ip登录时尽量重装软件再登录 不然结果都是一样的 3️⃣ 地区性 📍 除了上述两种因素外 有些地区是超高概率会有 甚至可以说100%会出现 比如+31、+852、+54……(当然…

22 Sept 2026, 05:24 UTC78 viewsread 25 September 2026
Photo

😀 API国外手机号接码服务 实体卡 🚩 只接收飞机的验证码(可以用来换绑飞机号) 🚩 可以防止意外掉号或者账号退出后可以接收验证码重新登录 🚩 首次购买接码有效期为30天,到期后可续费 虚拟卡价格为—60元(续费45元/30天) 实体卡价格为—100元(续费为100元/180天) —实体卡只能。注册。新号

22 Sept 2026, 05:14 UTC70 viewsread 25 September 2026
Photo

⚡️ Telegram 第三方客户端 官方客户端: iOS/iPadOS: Telegram Android: Telegram, Telegram X Windows: Telegram Desktop macOS: Telegram, Telegram Desktop(也叫Telegram Lite) Linux: Telegram Desktop 第三方客户端 iOS: * iMe Messenger * Nicegram * Turrit Android: * Turrit * iMe Messenger * Nekogram ⚠️ 注意: Telegram 官方没有直接出中文版, Android 上有个叫"Telegram中文版"是一个非官方客户端, 不是官方客户端, 并且还带有"会员"功能, 谨慎购买和使用

21 Sept 2026, 18:59 UTC73 viewsread 25 September 2026
Photo

✈️ 账号在登陆的时候出现的sms fee问题 ❗️ 首先 ,不是所有人都会有 至于已注册的账号出现的sms fee 问题前面已经针对性讲解过 ❗️ 常用的方式是通过第三方软件登陆 不花额外的钱 ❗️ 我理解有的人对第三方有顾虑和抵触 我也确实做不到改变所有人的思想 放别人那里我想处理方法与我的并无二样 且不说多数网上自助购买的甚至直接提示:sms fee问题与我们无关 ❗️ 不靠谱的第三方有很多 我自己也在用 靠谱的才会给你 我主用就是因为官方的无法达到我的工作需求 ❗️ 所以过程中出现sms fee问题 又实在不能接受第三方 可以随时提出并全额退款 另一方面也是节省时间 避免无意义的环节 ❗️ 我只是用最高效、最经济的方式解决问题 仅此而已 📍下面推荐点好用的第三方客户端 🔽🔽🔽🔽🔽🔽🔽🔽🔽🔽

21 Sept 2026, 11:52 UTC75 viewsread 25 September 2026
Photo

🚩一张图展示优质VPN与劣质VPN的区别 图左:机场专线 ➡️ IP干净且无风控 ➡️ 线路人数极少 适合任意场景 特别社交平台注册、养号、运营方面 像电报这样的平台 而且做海外业务的用户群体 基本上都用机场专线 劣质VPN在这个圈子里根本没人看得上 图右:劣质VPN ⚠️ 万人骑线路 ⚠️ 高风控 污染严重 这种只适合网页浏览、文件下载 但凡长期用在社交平台都会有封号的风险 所以这也是为什么大多数的劣质VPN只强调他们的速度 却从来不提及他们的质量 所以我们经常收到反馈:什么都没做就封了 也都是劣质vpn惹的祸 🗺节点安全性测试地址:http://ping0.cc

20 Sept 2026, 07:37 UTC113 viewsread 25 September 2026

✈️ 分享—来盘点下双向的原因 🤩 数量上限 私信的数量多了就双向 常见范围5-6个左右后双向 🤩 广告双向 作为第一种的延伸 我自己也经常收到广告 都是直接点的拉黑+举报 不需要有很多次 别人点几次通常就直接双向了 🤩 IP质量 目前依然有大量的小白用户因不懂而使用ip质量极差的vpn ip质量差有时候会什么都没干就双向了 更甚者封号 🤩 地区属性差 常见与1~3个月左右的账号 账号来源滥用极大的地区 私信一两个就双向 不会超过三个 🤩 地区隔离 +86 或 +852 有概率无法主动私信海外账号 但和同地区就可以 这个机制双向对待 ⚠️基本上你们自己就可以自检双向原因是因为什么了 🚩远离垃圾地区 🚩要用ip干净的vpn 🚩好效果离不开正确使用

20 Sept 2026, 02:26 UTCviews —

面包的_卖号小屋 pinned «日常生活分享:@hzwddp8888 主营业务: 📱 tg飞机号 ⭐ tg会员代开 📱 tg频道刷粉 📱 外区苹果id,外国软件账号 ⭐️ tg星星购买,用于典藏礼物 🌏 api国外手机号码接码 ⛏ tg双向,限制,18禁解决方法»

18 Sept 2026, 14:21 UTC147 viewsread 25 September 2026

✈️ 如何把购买来的账号完全属于自己? 登陆 =》改密码 =〉 改邮箱 》 踢设备(需24小时后) ⚠️部分号可能没有邮箱,针对这个号如果二次登陆请先在新设备登陆,老设备的telegram对话框接验证码登陆后老设备再上退出! ⚠️如果进行了踢设备那么接码网址想再次接码就会提示账号已死亡!因为接码本来就依靠一台在登陆设备获取登陆验证码。 完成了以上操作号商拿回号码的几率基本为0,因为99%的号码都是通过虚拟卡注册。

18 Sept 2026, 11:04 UTC141 views0 reactionsread 25 September 2026
Photo

📱 苹果版电报下载方式: 使用美区ID登录苹果商城,直接搜Telegram下载。 美区ID获取: 1️⃣https://idshare001.me/goso.html 公用免费账号,但有风险 2️⃣付费购买小火箭的私人账号,电报软件免费 https://t.me/mianbaowu/9 联系:@Jim1_177777 双向: @hzwxdy1212bot

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

Mentions

Named by 3 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.

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

“面包的_卖号小屋” (@mianbaowu), 398 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/mianbaowu.

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.