Channel
@AvalonNote
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,504subscribers
+13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002269533605 |
|---|---|
| Type | Channel |
| Username | @AvalonNote |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/AvalonNote |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 00:33 | 1,504 | +2 |
| 9 Aug 2026, 23:32 | 1,502 | +12 |
| 7 Aug 2026, 07:12 | 1,490 | -1 |
| 6 Aug 2026, 20:05 | 1,491 | first reading |
20 posts held, back to 30 January 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 July 2026 |
|---|---|
| Posts held | 20 (30 January 2026 – 28 July 2026) |
| Views total | 750 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 18:14 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
30 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 43.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 43.3% | |
| 😭 | 7 | 23.3% | |
| 👍 | 6 | 20.0% | |
| 😱 | 3 | 10.0% | |
| 👏 | 1 | 3.33% |
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 30reactions 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 30 January 2026 to 28 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.
【更新公告 | 抽奖奖品现已支持自动拉黑设置】 管理员创建或编辑抽奖奖品时，可以设置中奖后的自动拉黑天数。 用户获得该奖品后，将自动进入抽奖黑名单，并在指定天数内无法再次参与抽奖；设置为 0 天则不启用该功能。 如果使用批量设置奖品，请在设置完奖品后点击编辑奖品，单独设置某个奖品的拉黑天数。 解除拉黑可以使用 /unblock 或者到期后自动解除，拉黑和解除拉黑请看 https://t.me/AvalonNote/27 ——Saber @RealSaberBot
【更新通告｜群组关联频道评论增益】 为鼓励大家参与频道帖子讨论，增加频道与群组之间的互动，系统已新增“群组关联频道评论增益”功能。 群组管理员可以在发言增益设置中开启频道评论增益，并设置每位用户每天可获得奖励的次数。 用户在群组关联频道的帖子下发表评论，且评论符合群组现有的积分发言规则，即可在每日奖励次数内必定获得一次额外发言增益。奖励积分沿用群组设置的增益积分范围，且不计入普通发言积分上限。 达到当天频道评论奖励次数后，评论仍可按照群组原有规则参与普通随机发言增益。 本次更新不影响原有发言增益功能。欢迎大家围绕频道内容积极交流、认真讨论。 ——Saber @RealSaberBot
❤4👍1
t.me 于 2026 年 7 月 13 日被移出全球 DNS；Telegram 官方文档确认 telegram.me 可作为等效链接域名。 Saber 已经调整业务兼容 telegram.me 域名，如果各位在使用过程中发现有任何问题，请向我们 @avalonv2bot 反馈，感谢。
【更新公告 | 抽奖关注群组授权流程优化】 我们收到了一些群组管理员的反馈：官方机器人创建按键关注抽奖时，如果设置了需要授权的关注群组或频道，每次发布都要重新授权，操作比较繁琐。 针对这个问题，本次将授权流程优化为“长期授权”。 当目标群组或频道管理员完成一次授权后，同一主群后续再次发布到同一目标时，不需要重复授权。每次使用长期授权发布抽奖时，系统都会私聊通知原授权管理员，通知中也提供“撤销长期授权”按钮；撤销后，下次再发布到该目标时需要重新授权。 本次优化在减少重复操作的同时，也保留了目标管理员的知情和撤销能力，避免群组或频道被长期使用而管理员不知情。 适用范围： 官方机器人 按键关注抽奖 设置关注群组或频道时需要目标管理员授权的场景 欢迎各位群组管理员使用和反馈。 ——Saber @RealSaberBot
👍3
【更新公告 | 抽奖功能现已支持“宝物条件”设置】 管理员创建抽奖时，可以在额外条件中选择指定宝物，并设置参与抽奖需要拥有的数量，或设置参与时消耗指定数量的宝物。这样抽奖可以和宝物系统直接联动，让宝物不再只用于收集和兑换，也能成为参与活动的一部分。 例如： 须拥有 1 个指定宝物才可参加抽奖 须消耗 2 个指定宝物才可参加抽奖 目前该功能支持口令抽奖、按键抽奖、发言抽奖。 我们也观察到，已有部分群组会为宝物人工赋予一些特别用途，例如积分对抗道具、身份权益等。这也会是宝物系统后续的重要优化方向：未来管理员可以为宝物配置更多由系统支持的特殊功能，让宝物具备更丰富的用途，进一步提高群组活动参与度。 欢迎各位群组管理员使用和反馈。 ——Saber @RealSaberBot
根据部分群组管理员的意见和反馈，Saber 官方机器人将于 7月1日 正式启用「频道/群组发布授权」机制。 启用后，如果抽奖创建人不是目标频道或群组的管理员，抽奖发布到该目标前，需要对应频道或群组管理员先完成授权，详见： https://t.me/AvalonNote/65 此机制仅针对 Saber 官方机器人。 克隆机器人服务不受影响，仍按当前流程使用。 创建抽奖流程会因此多一个授权步骤，但这是为了保护各位群组和频道的发布安全，感谢大家的反馈、支持与理解。
📢 关于 Saber 官方机器人「频道/群组发布授权」功能的投票征询
Shares as published. No per-option vote count is published by Telegram, so none is shown.
抽奖进度查询功能上线 现在活跃发言抽奖、按键关注抽奖中设置了发言门槛时，用户可以在群内发送： 抽奖进度 查看自己当前的完成度。 支持显示： · 当前发言完成进度 · 是否已达标 · 激励任务减免次数 · 每日每人最多查询 5 次 欢迎各位群组管理员和群组成员使用和反馈。 ——Saber @RealSaberBot
❤2
世界杯竞猜功能预热：群主提前熟悉，提升群组活跃度 四年一届的世界杯快开始了，各位群主们可以提前熟悉下我们的竞猜功能，为世界杯积分竞猜做好准备，有效提高群组活跃度和热度哦！ 详情点击： https://t.me/AvalonNote/17 https://t.me/AvalonNote/24
【更新通告｜积分商城自动上架】 为方便群组管理员提前配置商品售卖时间，系统已新增“积分商城自动上架”功能。 管理员在创建或编辑商品时，可以设置自动上架时间。到达设置时间前，商品会保持待上架状态；到达时间后，系统会自动上架商品，并在群内发送上架通知。 系统也会校验自动上架与自动下架时间：自动下架时间必须晚于自动上架时间。若配置不合法，系统会提示错误，请管理员重新填写。 本次更新不影响原有自动下架功能。欢迎各位群组管理员使用和反馈。 ——Saber @RealSaberBot
❤1
【更新通告｜积分周期调整提醒】 为减少群组积分清零设置错误带来的影响，系统已新增“积分周期调整提醒”。 当群组设置了积分清零规则时，系统会在执行前第 5 天、第 3 天、第 1 天，于每天 22:00 在群内发送提醒。 本次更新不改变原有积分清理规则，无需进行任何设置，系统会自动在执行前提醒。欢迎各位群组管理员使用和反馈。 ——Saber @RealSaberBot
群聊总结功能新增“每日自动发送昨日总结” 群组管理员现在可以在群组配置中设置每日发送时间。设置后，系统会在每天指定时间自动发送上一日完整群聊总结；不设置时间则不会自动发送。 本次更新支持额外设置一个备份群组或频道。开启后，每日总结会同时发送到本群组和备份目标，便于长期留存。设置备份目标前，请先把机器人加入对应群组或频道，并设置为管理员。 同时支持本群组自动置顶 12 小时。置顶只作用于本群组，备份目标收到的总结不会置顶。 欢迎各位群组管理员使用和反馈。 ——Saber @RealSaberBot
👏1
Showing the 12 most recent of 20 posts we hold for @AvalonNote. 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
📢 关于 Saber 官方机器人「频道/群组发布授权」功能的投票征询
Shares as published. No per-option vote count is published by Telegram, so none is shown.
关于“抽奖奖品积分交易系统”的调研
The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
是否要开放管理员发放宝物合成材料给成员的功能？
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 30 January 2026 to 28 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 2,472 of 1,169,250entries 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.
Named by 187 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
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.
“阿瓦隆通知站” (@AvalonNote), 1,504 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/AvalonNote.
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.