🧠 KOMmunity Learn x @LemonJetX is live with rewards for $KOMmunity! 💰 Reward Pool: 20,833 $LJT ⏳ Ends: 15th September, 2026 Start the quest: 👉 https://app.galxe.com/quest/Kommunitas/GCK6RtZt57 Don’t miss your chance to earn more $LJT!
❤3

Channel
@kommunitas_ann
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
24,217subscribers
-784 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001466227272 |
|---|---|
| Type | Channel |
| Username | @kommunitas_ann |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/kommunitas_ann |
Giveaways & airdrops — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 39% 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 |
|---|---|---|
| 18 Sept 2026, 05:18 | 24,217 | -27 |
| 16 Sept 2026, 02:41 | 24,244 | -18 |
| 14 Sept 2026, 09:57 | 24,262 | -28 |
| 12 Sept 2026, 16:01 | 24,290 | -43 |
| 10 Sept 2026, 13:36 | 24,333 | -81 |
| 7 Sept 2026, 08:41 | 24,414 | -55 |
| 4 Sept 2026, 16:16 | 24,469 | -34 |
| 3 Sept 2026, 00:25 | 24,503 | -26 |
| 2 Sept 2026, 00:33 | 24,529 | -22 |
| 31 Aug 2026, 21:46 | 24,551 | -22 |
| 30 Aug 2026, 19:33 | 24,573 | -25 |
| 29 Aug 2026, 18:27 | 24,598 | -18 |
| 28 Aug 2026, 20:42 | 24,616 | -15 |
| 27 Aug 2026, 20:23 | 24,631 | -9 |
| 26 Aug 2026, 18:45 | 24,640 | -12 |
| 25 Aug 2026, 20:33 | 24,652 | -10 |
| 24 Aug 2026, 19:46 | 24,662 | -38 |
| 23 Aug 2026, 07:54 | 24,700 | -39 |
| 21 Aug 2026, 16:08 | 24,739 | -23 |
| 20 Aug 2026, 17:14 | 24,762 | first reading |
35 posts held, back to 24 July 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 58 pages of 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. It is computed over the 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 35 (24 July 2026 – 3 September 2026) |
| Views total | 1,341 |
| Reactions total | 33 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:39 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.
Measured directly from 2 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.
494 reactions across 17 posts, in 12 distinct kinds. The most used accounts for 85.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 423 | 85.6% | |
| 🔥 | 18 | 3.64% | |
| 👍 | 14 | 2.83% | |
| 👏 | 11 | 2.23% | |
| 🤩 | 8 | 1.62% | |
| ❤🔥 | 6 | 1.21% | |
| ⚡ | 3 | 0.607% | |
| 🎉 | 3 | 0.607% | |
| 💯 | 3 | 0.607% | |
| 🐳 | 2 | 0.405% | |
| 🥰 | 2 | 0.405% | |
| 💋 | 1 | 0.202% |
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 35 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 503 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 24 July 2026 to 3 September 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.
🧠 KOMmunity Learn x @LemonJetX is live with rewards for $KOMmunity! 💰 Reward Pool: 20,833 $LJT ⏳ Ends: 15th September, 2026 Start the quest: 👉 https://app.galxe.com/quest/Kommunitas/GCK6RtZt57 Don’t miss your chance to earn more $LJT!
❤3
Kommunitas x LemonJet AMA 🎙 AMA Session: LIVE with John Mental, CMO of @LemonJetX! 20 winners will share the $200 $KOM prize pool 💰 AMA Voice (X Space): September 7, 09:00 AM UTC 👉 https://twitter.com/i/spaces/1yGBePblamrKN AMA Text (Telegram): September 7, 12:00 PM UTC 👉 t.me/kommunitas Got questions? Ask them live during the AMA. ➡️ LemonJet Social Media: Website | Twitter
❤5
🚀 Whitelist open: @LemonJetX $LJT is LIVE! Early access starts now. Skip staking and enter Public Sale Booster 1. 🗓 IKO Date: September 9, 2026 at 9 AM UTC Apply here: 👉 https://app.galxe.com/quest/Kommunitas/GC1XDtZcL1 Who’s joining the whitelist today? ❤️🔥 Leave a like and retweet: https://x.com/kommunitasnet/status/2095078028586184965
❤5
Hi $KOMmunity! 📣 The Swap/Bridge feature has been disabled, and the $KOM token swap is no longer available. For now, $KOM swap/bridge requests can only be processed manually by the Kommunitas team (self-bridging is disabled). Please submit your request via this form and we’ll process it within a maximum of 48 hours: Request Bridge/Swap here : https://kommunitas.net/swap Notes: • KOM (Polygon or Arbitrum) → KOM (B…
Hello $KOMmunity! Voting is OPEN for @LemonjetX $LJT 🚀 Lemon Jet is a fully on-chain game on Base, powered by Chainlink VRF, with provably fair gameplay and winning bets up to 50,000x. 🔹 IKO starts: September 9 2026 at 09:00 AM UTC 🔹 IKO Type: Secure IKO Secure your spot in the $LJT sale 👉 https://kommunitas.net/pool/LJT/PublicCross ❤️🔥 Give a like and retweet to burn more KOM: https://x.com/kommunitasnet/statu…
❤7
📢 KOM Manual Swap to BSC – Important Update Dear $KOMmunity, We would like to clarify that the KOM manual swap from Polygon and Arbitrum to BSC is currently only available for KOM tokens received through the unstaking process. Due to the price difference between KOM on Polygon and BSC, KOM tokens that were purchased or repurchased on Polygon, or obtained through swaps, are not eligible for the manual swap process.…
👍7❤6
Hi $KOMmunity! We're excited to announce @Heroarenagroup as our partner for the upcoming IKO! 🚀 Hero Arena Play is a decentralized turn-based PvP blockchain game. Choose your faction, stake tokens, and battle players worldwide. Stay tuned for more details. ❤️🔥 Leave a like and repost: https://x.com/kommunitasnet/status/2090728010634997900
❤13
Hi $KOMmunity, Alberich Token $ALBRH’s Uniswap liquidity is officially locked! 🔒 You can independently verify the lock here: 👉 team.finance/view-coin/0x7adbfd873084db714a57ed648ee69aa4627cb998?name=Alberich%20Token&symbol=ALBRH&chainid=0x1 This adds an extra layer of post TGE security confirmation for the project.
👏7
Hi $KOMmunity! We’re thrilled to welcome @LemonjetX as an official partner for our upcoming IKO! 🚀 Lemonjet is a decentralized GambleFi Web3 game, fully on-chain with rewards controlled by smart contracts. IKO date coming soon. ❤️🔥 Leave a like and repost: https://x.com/kommunitasnet/status/2087469094471888905
❤6
🔥 $ALBRH IS NOW LIVE ON UNISWAP! Hi $KOMmunity, @AlberichToken $ALBRH has officially listed and trading is now open! 🎉 ⛓️ Chain: Ethereum 🦄 DEX: Uniswap V3 📝 Contract: 0x7adbfd873084db714a57ed648ee69aa4627cb998 👉 Trade now: https://app.uniswap.org/explore/tokens/ethereum/0x7AdbFd873084dB714A57eD648ee69Aa4627Cb998
❤3
🚨 Official Notice – Alberich Token ($ALBRH) Dear $KOMmunity, We would like to provide an important clarification regarding the Alberich Token ($ALBRH) and the warning currently displayed on Uniswap. According to the Alberich Token team, the official Ethereum contract address for $ALBRH is: 0x7AdBfd873084dB714A57eD648ee69Aa4627Cb998 The project team has informed us that the “Impersonator token detected” warning cu…
📢 $ALBRH TGE & Listing Update Dear $KOMmunity, We have received an update from the Alberich Token team regarding the ongoing listing delay. 🔹 $ALBRH TGE is still proceeding today. 🔹 The delay is caused by a technical issue during the final Uniswap V3 liquidity activation through the project’s multisig Safe wallet. 🔹 The project team has confirmed that the liquidity and tokens are already in place and they are curr…
Showing the 12 most recent of 35 posts we hold for @kommunitas_ann. 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.
@kommunitas_ann edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 6 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 16 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 56 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Kommunitas Announcement Channel” (@kommunitas_ann), 24,217 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/kommunitas_ann.
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.