Channel
@bannergressnews
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,705subscribers
+4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001443037898 |
|---|---|
| Type | Channel |
| Username | @bannergressnews |
| Created | 19 March 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/bannergressnews |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 22:18 | 2,705 | +4 |
| 13 Aug 2026, 08:38 | 2,701 | -5 |
| 9 Aug 2026, 23:33 | 2,706 | +4 |
| 7 Aug 2026, 03:07 | 2,702 | +1 |
| 6 Aug 2026, 11:06 | 2,701 | no change |
| 6 Aug 2026, 09:42 | 2,701 | first reading |
20 posts held, back to 13 April 2023 — 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.
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 1 April 2026. An engagement rate over an empty window would be a number about nothing.
789 reactions across 20 posts, in 32 distinct kinds. The most used accounts for 38.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 300 | 38.0% | |
| ❤ | 177 | 22.4% | |
| 👏 | 60 | 7.60% | |
| 😱 | 35 | 4.44% | |
| 🎉 | 32 | 4.06% | |
| 😢 | 30 | 3.80% | |
| 🍾 | 26 | 3.30% | |
| 🥰 | 25 | 3.17% | |
| 🔥 | 21 | 2.66% | |
| 😭 | 17 | 2.15% | |
| 👌 | 12 | 1.52% | |
| 💩 | 11 | 1.39% | |
| 🏆 | 5 | 0.634% | |
| ❤🔥 | 4 | 0.507% | |
| 💯 | 4 | 0.507% | |
| 🤣 | 3 | 0.38% | |
| 🤩 | 3 | 0.38% | |
| 🫡 | 3 | 0.38% | |
| ⚡ | 2 | 0.253% | |
| 🍌 | 2 | 0.253% | |
| 12 further kinds | 17 | 2.15% |
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 20 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 789reactions 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 13 April 2023 to 1 April 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.
We are aware of an issue with mission images not loading, or taking a very long time to load. This has some further effects: * Creating a banner fails if such a mission is part of the banner * Refreshing a mission fails (with IITC and creator plugin), if the mission is part of a banner, and the banner picture has to be recalculated * Mission images fail to load in IITC and Ingress itself Issue seems to be fixed.
❤2
Agent verification is back! It took us Niantic soon™ to finish, but you can now verify your Ingress account again. Verified accounts allow you to edit your own banners (add planned offline dates, replace offline missions, add warnings etc.) Verification can be done at https://bannergress.com/account If you have already verified in the past, the old verification is still valid.
🍾26🥰17👍5🔥5❤2🙏1
Dear agents, today between 19:00 UTC and 20:00 UTC server maintenance will occur, during which bannergress.com will be down, or banners may appear missing. We will inform you about the end of maintenance. Server Maintananace has Concluded all schould be back to normal. Please write any findings into the support group.
👍14🤗2😱2✍1
Dear Agents, Today Jan 26th as from UTC 1300hrs major server maintenance will occur during which bannergress.com and connected services might be down at times. Once Server maintenance has concluded we will inform. Server Maintananace has Concluded all schould be back to normal. Please write any findings into the support group.
👍27🫡3⚡2🔥2
We are aware of an issue with missing banner addresses when creating new banners. This is most likely caused by errors in the Google Maps API. If your newly created banner has no address, please tell us in the support channel.
❤14
Bannergress is available again
🎉30❤12
Bannergress is currently not available, due to network issues
😢9😁2🙈2
Bannergress server is up and running again
👏43❤5🤩3
The Bannergress server is currently down, most likely due to an issue with the provider
😢20👍2
Dear Agents, Today Jul 03 between approximately 2100utc - 2300utc Server maintenance will occur, including switching of DNS records. We will inform once Maintenance has concluded. Server maintenance has finished all services should be up and running. If you encounter errors please report them in the support group.
❤23👍13👌5😱3🕊1
Dear agents, Niantic has recently announced changes to the community forum. Therefore, the Bannergress agent verification process won't work anymore starting April 1st. We are currently investigating alternatives. Verifications completed before April 1st are not affected. If you plan on editing your own banners on Bannergress, we recommend that you verify your account in the next few days.
😭17😱10❤7👍4
The issue with the Bannergress IITC plugin has been resolved with the latest version v0.5.3 v0.5.4.
👍17🎉2
Showing the 12 most recent of 20 posts we hold for @bannergressnews. 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 — 1,382,677 of 1,481,306entries 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 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Bannergress News” (@bannergressnews), 2,705 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bannergressnews.
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.