Channel
@CognitosAnnoucement
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
733subscribers
-33 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001591755196 |
|---|---|
| Type | Channel |
| Username | @CognitosAnnoucement |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/CognitosAnnoucement |
Crypto & trading — 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 84% 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 |
|---|---|---|
| 13 Sept 2026, 22:19 | 733 | -8 |
| 6 Sept 2026, 21:01 | 741 | -7 |
| 29 Aug 2026, 04:33 | 748 | -6 |
| 21 Aug 2026, 12:37 | 754 | -10 |
| 14 Aug 2026, 15:08 | 764 | -1 |
| 8 Aug 2026, 04:15 | 765 | -1 |
| 7 Aug 2026, 08:33 | 766 | no change |
| 7 Aug 2026, 08:26 | 766 | first reading |
20 posts held, back to 6 February 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 20 posts for this entry, the most recent from 14 December 2024. An engagement rate over an empty window would be a number about nothing.
98 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 30 | 30.6% | |
| ❤ | 22 | 22.4% | |
| ❤🔥 | 14 | 14.3% | |
| 👍 | 12 | 12.2% | |
| 🥰 | 9 | 9.18% | |
| 👏 | 6 | 6.12% | |
| 🍾 | 4 | 4.08% | |
| 🤔 | 1 | 1.02% |
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 18 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 98 reactions 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 6 February 2024 to 14 December 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.
Congratulation to Xeno AI that passed Smart Contract Audit Process by Cognitos Name: Xeno AI Website: https://xenoai.network/ Smart Contract: Ethereum (ERC-20) Smart Contract Audit Report : ▫️0xa3637Da59d9007F324C2628Ebdd17dc1a839c394 https://www.cognitos.io/xenoai-audit https://x.com/CognitosAudit/status/1867950037998981224 Xeno AI Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos Off…
❤2🔥2❤🔥1👍1👏1
Congratulation to Skyren that passed Smart Contract Audit Process by Cognitos Name: Skyren Website: https://skyren.io/ Smart Contract: Polygon 0xBa74014e2A8ab23b14f7D6d067494A0Bf1567bB2 Smart Contract Audit Report : ▫️https://www.cognitos.io/skyren-audit https://x.com/CognitosAudit/status/1864376957087174804 Skyren Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos Official Team: @InfoCo…
❤1🔥1
This KYC Verification certifies that the mentioned project has been virtually verified by Cognitos. 🎖This Certificate is Proudly Presented To Skyren ▫️Full KYC Report https://x.com/CognitosAudit/status/1864377220741124407 Skyren Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos Official Team: @InfoCognitos Cognitos Official Links: 🌍www.cognitos.io | 📝X | 📰Medium | 🤖Discord | 📷Instagram |…
❤1🔥1
Congratulation to Lightning McQueen that passed Smart Contract Audit Process by Cognitos Name: Lightning McQueen Website: - Smart Contract: Binance (BEP-20 0x95413d9c5a796435dc5667703D81eb3580D5bAF9 Smart Contract Audit Report : ▫️https://www.cognitos.io/lightningmcqueen-audit https://x.com/CognitosAudit/status/1848357030798753828 Lightning McQueen Official Links: ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos…
🔥2❤1🥰1
Congratulation to Bells Coin that passed Smart Contract Audit Process by Cognitos Name: Bells Coin Website: https://bellscoin.dog/ Smart Contract: Ethereum (ERC-20) 0x55fb4f2abfaa938e0c756fec413612f326896577 Smart Contract Audit Report : ▫️https://www.cognitos.io/bellscoin-audit https://x.com/CognitosAudit/status/1838232713301545385 Bells Coin Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Co…
🔥3❤2🥰1
Congratulation to Xyzmercoin that passed Smart Contract Audit Process by Cognitos Name: Xyzmercoin Website: https://xyzmercoin.xyz/ Smart Contract: Binance (BEP-20) 0xf67d3a33ef4ad4316b2ca6be257a4d79fd2088c2 Smart Contract Audit Report : ▫️https://www.cognitos.io/xyzmercoin-audit https://x.com/CognitosAudit/status/1828291171963314250 Xyzmercoin Official Links: 🌍Website | ✉️Telegram | 📝X | Play the Game! —————––––…
❤2❤🔥1👍1🔥1
This KYC Verification certifies that the mentioned project has been virtually verified by Cognitos. 🎖This Certificate is Proudly Presented To Xyzmercoin ▫️Full KYC Report https://x.com/CognitosAudit/status/1828291542999859605 Xyzmercoin Official Links: 🌍Website | ✉️Telegram | 📝X | Play the Game! —————––––––––––––––––––– Cognitos Official Team: @InfoCognitos Cognitos Official Links: 🌍www.cognitos.io | 📝X | 📰Medium …
❤2👍2🔥2❤🔥1
This KYC Verification certifies that the mentioned project has been virtually verified by Cognitos. 🎖This Certificate is Proudly Presented To RebirthAI ▫️Full KYC Report https://x.com/CognitosAudit/status/1823287177121550601 RebirthAI Official Links: 🌍Website |📝X —————––––––––––––––––––– Cognitos Official Team: @InfoCognitos Cognitos Official Links: 🌍www.cognitos.io | 📝X | 📰Medium | 🤖Discord | 📷Instagram | 📹Youtub…
🔥1
This KYC Verification certifies that the mentioned project has been virtually verified by Cognitos. 🎖This Certificate is Proudly Presented To Xei ▫️Full KYC Report https://x.com/CognitosAudit/status/1801449230558707816 Xei Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos Official Team: @InfoCognitos Cognitos Official Links: 🌍www.cognitos.io | 📝X | 📰Medium | 🤖Discord | 📷Instagram | 📹Yout…
❤1🔥1🥰1
Congratulation to Octoblock that passed Smart Contract Audit Process by Cognitos Name: Octoblock Website: https://octoblock.io// Smart Contract: Binance Smart Chain (BEP-20) 0x49eb799dbd56c20c5d67f99ffa3dd5fde0c2da17 Smart Contract Audit Report : ▫️https://www.cognitos.io/octoblock-audit ▫️NFT Certificate https://x.com/CognitosAudit/status/1778462062022438980 Base Buy Official Links: 🌐Website |✉️Telegram | 📝X ———…
Congratulation to OctoBlock that passed Smart Contract Audit Process by Cognitos Name: OctoBlock Website: https://octoblock.io/ Smart Contract: Binance (BEP-20) 0x49eB799DBd56C20C5D67F99FfA3DD5fde0C2dA17 Smart Contract Audit Report : ▫️https://www.cognitos.io/octoblock-audit https://x.com/CognitosAudit/status/1782070683960541428 Octoblock Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognito…
👍2❤1❤🔥1🤔1
This KYC Verification certifies that the mentioned project has been virtually verified by Cognitos. 🎖This Certificate is Proudly Presented To OctoBlock ▫️NFT Doc Certificate ▫️KYC Doc Certificate ▫️Full KYC Report https://x.com/CognitosAudit/status/1782071285339869273 OctoBlock Official Links: 🌍Website | ✉️Telegram | 📝X —————––––––––––––––––––– Cognitos Official Team: @InfoCognitos Cognitos Official Links: 🌍www.co…
🔥3👏2❤🔥1
Showing the 12 most recent of 20 posts we hold for @CognitosAnnoucement. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 17 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.
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.
@CognitosAnnoucement named 2 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Cognitos - Announcement” (@CognitosAnnoucement), 733 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/CognitosAnnoucement.
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.