Telegram RegisterThe public register of Telegram

Channel

FanrrCloud通知频道

@Fanrr_NOC

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

1,355subscribers

+12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002076031777
TypeChannel
Username@Fanrr_NOC
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Fanrr_NOC

Growth

1,3421,3551,348.57 August 2026 — 1,343 subscribers7 August 2026 — 1,342 subscribers10 August 2026 — 1,348 subscribers13 August 2026 — 1,355 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +12. 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 1,340–1,357 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:451,355+7
10 Aug 2026, 12:521,348+6
7 Aug 2026, 15:001,342-1
7 Aug 2026, 09:171,343first reading

Engagement

20 posts held, back to 28 October 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

39 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 63235998960205188791333.3%
👍1230.8%
custom 54720057162837609201025.6%
410.3%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 11 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 39reactions 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 28 October 2024 to 14 July 2025, 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

14 Jul 2025, 08:32 UTC≈4,790 views16 reactionsread 7 August 2026

全网通报,节点连通性尽力而为,公网节点暂时下架

custom 63235998960205188797👍5custom 547200571628376092031

13 Mar 2025, 12:41 UTC≈7,240 views1 reactionsread 7 August 2026

已修复 部分权限组无法获取完整节点 emby部分用户无法注册

👍1

8 Feb 2025, 10:10 UTC≈7,950 views8 reactionsread 7 August 2026
Sticker

Sticker, posted without a caption

custom 547200571628376092071

7 Feb 2025, 10:13 UTC≈6,720 views6 reactionsread 7 August 2026

📣📣📣📣📣📣📣📣 ↔️助力频道可以获得套餐了! 🐇每助力3次频道可以获得50G流量 ⚠️不限时套餐直接添加50g ⚠️限时套餐顺延5天时间 ⚠️没有套餐可获得50g月付套餐(不可续费,内鬼组) ⚠️助力频道后取消助力会成倍删除流量(套餐时间) ⚠️助力之后官网发送工单带上截图和TG用户名给你添加流量,发不了图片的使用图床发链接 图床:我爱玩原神 ⚠️https://t.me/boost/Fanrr_NOC 限时活动

custom 63235998960205188796

3 Feb 2025, 00:51 UTC≈4,920 viewsread 7 August 2026

由于部分改动造成目前订阅无法正常下发,正在紧急修复 已完成 专用客户端不受影响

28 Jan 2025, 17:14 UTC≈4,580 views4 reactionsread 7 August 2026

祝所有人新的一年 SSH 安全稳固,服务器交换机高效运转,光纤坚韧畅通无阻,爬虫全部远离你家,收录天天上首页,一年到头网络环境平稳无波,网关响应如飞,广播 IP 稳定可靠,备案一审即过,数据库高速运行,网站永不 502,SSL 加密全面保障,服务器数据稳如泰山,流量暴涨带宽充足,并发轻松应对,ping 延迟超低,Windows 开机流畅如新,Linux 稳定高效,macOS 开机顺畅优雅,服务器 iDRAC/iLO/IPMI/KVM 随时在线,路由器坚不可摧,路由表精准高效,交换机运行顺畅,防火墙滴水不漏,无线信道协调一致,收光全满格,ESXi 存储池稳定无虞,DHCP 高效分配,NAS 数据安全无忧,光模块性能卓越,POE 稳定供电,光纤连接稳定,光猫温润如初,电表准确计量,UPS 持久续航,CN2 路径直达全球,BGP 稳定可靠,线路畅通无阻,运营商支持全面升级,公网 IP 想用就有,服务器端口全部开放,服务商稳定可靠,服务

👍4

28 Jan 2025, 16:00 UTC≈3,030 viewsread 7 August 2026

新年快乐朋友们,以下链接获取兑换码 http://www.sixin.cc/message/6796ab41c70b3 http://www.sixin.cc/message/6796abe461e28 http://www.sixin.cc/message/6796ac031ff5b http://www.sixin.cc/message/6796ac10ae304

26 Jan 2025, 21:34 UTC≈2,950 views3 reactionsread 7 August 2026
Photo

家人们新年快乐!祝大家过个好年,并且过好一年! 按照惯例,我们来圈各位的压岁钱啦 全场8折: 2025GO! 半年付及以上75折: 2025GO!! [2025/01/29 00:00 ~ 2025/02/07 00:00] 生效 并且在29日0点将会准时掉落 月付x3 年付x1 的订阅 (阅后即焚) 现站点主题可能存在优惠与实付颠倒问题,不影响实际使用

👍21

25 Jan 2025, 23:12 UTC≈2,350 viewsread 7 August 2026

没活了家人们,不小心给EMBY的母鸡关机了,得等机房上班才能用 已恢复

23 Jan 2025, 08:48 UTC≈3,440 views0 reactionsread 7 August 2026
Photo

什么什么?你怎么知道 Fanrr 和 1111Emby 合作了!!? 持任周期性有效订阅均可注册使用,点击人机: @Fanrr_emby_bot 并发送 /cz 注册账户

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

Citation-graph rank

Citation-graph rank — 869,215 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“FanrrCloud通知频道” (@Fanrr_NOC), 1,355 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Fanrr_NOC.

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.