Telegram RegisterThe public register of Telegram

Channel

Notice

@notice

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

4,680subscribers

+8 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1002056922561
TypeChannel
Username@notice
Created29 April 2024measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/notice

Growth

4,6684,6804,6745 August 2026 — 4,672 subscribers6 August 2026 — 4,672 subscribers6 August 2026 — 4,669 subscribers9 August 2026 — 4,668 subscribers13 August 2026 — 4,680 subscribers5 August 202613 August 2026
5 measurements spanning 7 days, net +8. 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 4,666–4,682 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 02:034,680+12
9 Aug 2026, 17:224,668-1
6 Aug 2026, 21:544,669-3
6 Aug 2026, 03:524,672no change
5 Aug 2026, 19:154,672first reading

Engagement

19 posts held, back to 29 April 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 7 pagesof 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 19 posts for this entry, the most recent from 30 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
33s
Average length
33s

Measured directly from 1 video 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.

Recent posts

20 Dec 2025, 21:30 UTC≈13,500 viewsread 12 August 2026

🔔All bans (Except TOS Violations) lifted. 🔓Rejoin @chatter if you’re cleared. ⛔️ Ignore if not relevant.

30 Aug 2025, 01:03 UTC≈24,700 viewsread 12 August 2026
Photo

Leaderboard Rewards V2: Level 10 - $20 - CLAIMED Level 20 - $40 CLAIMED Level 30 - $60 CLAIMED Level 40 - $80 CLAIMED Level 50 - $120 CLAIMED Level 60 - $150 CLAIMED Level 70 - $200 CLAIMED Level 80 - $250 CLAIMED Level 90 - $500 CLAIMED Level 100 - $1000 - CLAIMED Rewards will be crossed off once claimed. Information You can claim only one reward. Reach a level and choose to claim or push higher. Any spamming or

26 Apr 2025, 11:09 UTC≈24,200 viewsread 12 August 2026

🔔All bans (Except TOS Violations) lifted. 🔓Rejoin @chatter if you’re cleared. ⛔️ Ignore if not relevant.

2 Jan 2025, 07:17 UTC≈27,400 viewsread 12 August 2026

All warnings have been reset for a fresh start in 2025! 🎉 Let’s keep the chat friendly and enjoyable for everyone moving forward. On a side note, special shoutout to @goonestt and @zachary, who together have racked up a combined total of 500 warnings... You two really know how to make things interesting! 😅 Let’s keep it cool this year!

30 Dec 2024, 04:12 UTC≈28,100 viewsread 12 August 2026
Photo

We’re Looking for Moderators! If you're interested, go to @ChatterApplicationBot and complete the form. Applications will be reviewed throughout the week. Do not message admins about your application.

11 Nov 2024, 02:55 UTC≈124,000 viewsread 12 August 2026

Starting now, all messages in @chatter will automatically delete after 24 hours. This update is aimed at keeping the chat cleaner and more organized. Soon, we’ll be limiting media/sticker usage to users with a certain level on Beem to help prevent spam and the sharing of inappropriate content. Note: This change will not affect your current levels.

11 Oct 2024, 21:29 UTC≈112,000 viewsread 12 August 2026

To receive these airdrops, you need to join @chatter and @notice.

11 Oct 2024, 21:29 UTC≈112,000 viewsread 12 August 2026
Video

🦋 ​Check for 🪙 10 TON ($52.39). 💬 Password: OGU

11 Oct 2024, 21:28 UTC≈103,000 viewsread 12 August 2026

Starting today, we will be adding Airdrops to chatter. Airdrops will be worth up to $100 a week and will be spread out randomly throughout the week. Airdrops will have channel and/or group join requirements to enable claiming, of which will be rotated periodically. These join requirement changes will always be announced in @Notice beforehand To a claim an airdrop you will be required to enter a custom a password of

5 Oct 2024, 01:13 UTC≈139,000 viewsread 12 August 2026

All previously banned users are now unbanned and can rejoin @chatter. Please note that users who violated Telegram's Terms of Service will remain banned. If this message does not apply to you, feel free to ignore it.

Showing the 12 most recent of 19 posts we hold for @notice. 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 — 949,509 of 1,160,990entries 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 1 registered channel — 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.

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.

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.

“Notice” (@notice), 4,680 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/notice.

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.