Channel
@fm_safe
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,951subscribers
+6 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001529641408 |
|---|---|
| Type | Channel |
| Username | @fm_safe |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/fm_safe |
Adult — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 11 Oct 2026, 08:56 | 2,951 | -3 |
| 5 Oct 2026, 08:37 | 2,954 | -2 |
| 26 Sept 2026, 19:22 | 2,956 | -10 |
| 17 Sept 2026, 07:15 | 2,966 | -3 |
| 13 Sept 2026, 15:19 | 2,969 | -3 |
| 9 Sept 2026, 21:55 | 2,972 | -4 |
| 4 Sept 2026, 08:01 | 2,976 | +4 |
| 31 Aug 2026, 14:07 | 2,972 | -8 |
| 28 Aug 2026, 12:15 | 2,980 | +5 |
| 25 Aug 2026, 10:18 | 2,975 | +16 |
| 22 Aug 2026, 07:36 | 2,959 | +3 |
| 19 Aug 2026, 03:13 | 2,956 | +1 |
| 16 Aug 2026, 07:08 | 2,955 | +11 |
| 12 Aug 2026, 08:38 | 2,944 | -1 |
| 11 Aug 2026, 10:48 | 2,945 | first reading |
7 posts held, back to 10 May 2024 — 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 7 posts for this entry, the most recent from 15 May 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos 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.
18 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 50.0% | |
| 👍 | 9 | 50.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 7 of the 7 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 10 May 2024 to 15 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
坐标: 广州 佛山 🉑代开🉑上门（🌟广佛靠谱经济，人照合一，各位老板请放心下单） 选妹频道：https://t.me/gfudgjff：https://t.me/gfudgjff 咨询客服：@rdhfrufdhhf 大队长备案(补贴）： https://t.me/DearAgent 加入扫雷预备队： https://t.me/saolei_sapper
❤3👍3
深圳北附近抓龙筋个人🍓情趣丝袜诱惑👏互动调情💋前列腺保养➕前列腺高潮➕女王调教🍓多重释放🍓让你爱上小敏💞深圳均可上门💋 #龙华小敏 #抓龙筋 #前列腺高潮 #丝袜恋足 #女王调教 QQ: 459807786 QQ：3648985719 电话19169701569（微信同号） 电话13262539762（微信同号） ☎️私聊： @xmam69 ☎️频道： https://t.me/xm68686 大队长帮约： https://t.me/DearAgent 加入扫雷预备队： https://t.me/saolei_sapper
❤1
坐标: 深圳南山❤️（柔式抓龙筋）💋 美女个人频道：https://t.me/Hksksnsnsj 加美女好私教：https://t.me/hjnbxjdj 大队长备案(补贴）： https://t.me/DearAgent 加入扫雷预备队： https://t.me/saolei_sapper
👍2❤1
坐标：深圳 福田丝足姐妹花 美女个人频道：https://t.me/tzjbs258 加美女好私教：https://t.me/TDHKD 加入扫雷预备队： https://t.me/saolei_sapper
👍1
坐标：深圳 龙华/龙岗00后丝足抓龙筋 美女个人频道：https://t.me/zglj3653 加美女好私教：https://t.me/TJXVNHC 加入扫雷预备队： https://t.me/saolei_sapper
❤2👍2
坐标：广州天河 🌹小静(平模) 美女个人频道：https://t.me/bshxjds 加美女好私教 https://t.me/bbbbbaao 与你号：aa19980 大队长备案(补贴）： https://t.me/DearAgent 加入扫雷预备队： https://t.me/saolei_sapper
坐标: 广州 佛山 🉑代开🉑上门（🌟广佛靠谱经济，人照合一，各位老板请放心下单） 选妹频道：https://t.me/gfudgjff：https://t.me/gfudgjff 咨询客服：@rdhfrufdhhf 大队长备案(补贴）： https://t.me/DearAgent 加入扫雷预备队： https://t.me/saolei_sapper
❤2👍1
Showing the 7 most recent of 7 posts we hold for @fm_safe. 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.
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.
@fm_safe named 3 handles 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“安全区（PDCA优质资源上榜推荐)” (@fm_safe), 2,951 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/fm_safe.
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.