Telegram RegisterThe public register of Telegram
Telegram profile photo for 铁甲群黑榜投诉

Channel

铁甲群黑榜投诉

@tiejiaheibang

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

695subscribers

-2 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-1003473250632
TypeChannel
Username@tiejiaheibang
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/tiejiaheibang

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Growth

693702697.57 August 2026 — 697 subscribers8 August 2026 — 697 subscribers15 August 2026 — 693 subscribers22 August 2026 — 700 subscribers28 August 2026 — 701 subscribers4 September 2026 — 699 subscribers13 September 2026 — 700 subscribers1 October 2026 — 702 subscribers12 October 2026 — 695 subscribers6957 August 202612 October 2026
9 measurements spanning 65 days, net -2. 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 692–703 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 00:22695-7
1 Oct 2026, 06:00702+2
13 Sept 2026, 08:00700+1
4 Sept 2026, 20:16699-2
28 Aug 2026, 14:44701+1
22 Aug 2026, 12:13700+7
15 Aug 2026, 07:47693-4
8 Aug 2026, 02:19697no change
7 Aug 2026, 17:54697first reading

Engagement

8 posts held, back to 6 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 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 8 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

5 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 80.0% of them.

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

Measured over the 8 most recent posts we hold, published 6 June 2026 to 27 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.

Recent posts

27 Jul 2026, 13:50 UTC401 viewsread 8 August 2026

#黑榜 【投稿人】:无心 【踩雷店铺】: 好妹妹 【踩雷女仆】:钱多多 【时间】:7月 【经过】:今天本来说去打卡满姐,看之前的测评和评价都挺好。约好11点,最后一个尾钟。有点事耽搁了,提前有跟客服沟通,晚了10多分钟。到了后妹子上来说等我了好久,上个客人提前下钟了,说一天都是满的,现在好累。就想着快点结束。钟上体验一般,没多久就直接进入主题,涂油上手,15分钟左右结束,然后就躺着看电视了,最后提前20分钟让我结账走人了。后续跟客服沟通,妹子状态不好可以不上这个钟的,提前说了,我也可以不过来的,一趟16公里,也挺远挺累的。 【是否需要管理协助沟通】:否 【店家处理结果/有无补偿】:说是给100优惠券。

26 Jul 2026, 13:55 UTC435 viewsread 8 August 2026

投稿#黑榜模块 【投稿人】:猫猫毁灭世界 【踩雷店铺】: 古茗 【踩雷女仆】:无 【时间】:7.25 【经过】:昨天约好的3点,今天因为是开高速过去,大概100公里一个半小时路程,特意出发前看过tg,没消息1.20就出发了。开到楼下停好车2.47,看了手机才发现1.49通知我不来了。看截图妹子上午10.57请的假,到我这里1.49才跟我说,问为什么不早说,我也不至于白跑,答曰中午没醒。最可气的是临时鸽子浪费别人那么多时间,就随便来了句下次来给你优惠,全程没有任何一句道歉,将心比心,我真想不出对面是不是个正常人类。 【是否需要管理协助沟通】:否 【店家处理结果/有无补偿】:#下次优惠,和没说一样

25 Jul 2026, 09:15 UTC416 viewsread 8 August 2026

#黑榜 【投稿人】:Sinoyuri 【踩雷店铺】: #塔菲喵 【踩雷女仆】:#客服小埋 【时间】:2026-07-25 【经过】:神人商家客服今天凌晨提前预约的女仆,客服回应好的,今天凌晨四点半突然问我来不来,拢共几小时后后就约给别人,你们就这么做客服?谁睡醒第一时间看tg,还优惠100,本来100券就好弄,而且已经有50优惠了,还这么搞,跑一趟都不止100了,来个🥚 【是否需要管理协助沟通】:不需要协助沟通,东站的店也约过几十个钟了,第一次遇到这么离谱的,避雷了 【店家处理结果/有无补偿】:无

20 Jul 2026, 06:52 UTC681 views3 reactionsread 8 August 2026

投稿#黑榜模块 【投稿人】:一直没花钱 【踩雷店铺】: #灰太狼女仆乐园 原阿里巴巴 【踩雷女仆】:1️⃣捏捏 2️⃣纯儿 【时间】:2026-07-18 【经过】:事情的起因很简单,周末无聊和朋友CJ,也是看了店铺内的测评和了解店铺外的消息才出发的。 先说下统一的雷点吧。 1️⃣时间问题:周五的时候和客服约好从外地赶过去,预约时间均为2:30,预约2H,也付了定金,且和客服再三确认过时间不要让女仆迟到。我是2:20就已经到了,然后开始询问客户女仆还多久到,客服说堵车十分钟到,中途也问了两次多久到,都是说十分钟到。理由是堵车,快到小区门口了。最后的结果是纯儿大概是在2:50分左右到的,捏捏是在3:10分左右到的。基本上两个都迟到了半个小时甚至四十分钟左右。 2️⃣店铺设施问题:这个就一笔带过吧,店铺位置是那种比较老的小区,较为简陋。店铺内异味是比较严重的,且如果要洗澡什么的甚至都没有可替换的拖鞋等东西,环境只能说比较差吧。 3️…

❤3

5 Jul 2026, 14:34 UTC900 views2 reactionsread 8 August 2026

#黑榜 【投稿人】:谭佩霖 【踩雷店铺】: #JOJO 【踩雷女仆】:#橙橙+客服 【时间】:7月 【经过】:首先是预约过程,预约的外派8-10,并得到了客服的确认,随后客服问我能不能换成9-11,我表达了拒绝,然后客服告诉我前面客人迟到+补妆,所以推迟,然后8.09分告诉我9点出发,实际25分钟的打车路程,9.50分人才到。大概率是中间加了一个单钟。 第二个踩雷的是上钟过程,过程中“多次”询问女仆是否能脱上衣,都得到了否认。询问原因告诉我一直都是不脱上衣的。实际是我之前到店单钟都是卸甲顺利,外派双钟反而上衣都不肯脱了。并且舌吻的过程中没碰到过对方的舌头,只有一个空空荡荡的口腔,被卡麻了。瞬间下头,然后就让她退钟回去了。 【是否需要管理协助沟通】:不需要 【店家处理结果/有无补偿】:商家退了定金,也没收路费。

❤1👍1

Showing the 8 most recent of 8 posts we hold for @tiejiaheibang. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“铁甲群黑榜投诉” (@tiejiaheibang), 695 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/tiejiaheibang.

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.