Channel
@covertcove
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
775subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001333656684 |
|---|---|
| Type | Channel |
| Username | @covertcove |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/covertcove |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 22:02 | 775 | -3 |
| 15 Aug 2026, 10:25 | 778 | -1 |
| 8 Aug 2026, 13:50 | 779 | -2 |
| 8 Aug 2026, 01:47 | 781 | no change |
| 7 Aug 2026, 19:30 | 781 | first reading |
20 posts held, back to 5 June 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 1 pageof 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 7 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 7 August 2026) |
| Views total | 128 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:47 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.
17 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5375327144912128057 | 17 | 100.0% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.
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 6 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 17reactions 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 5 June 2026 to 7 August 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.
Covert Cove v61.141 change log: 1) Fixed an error where listing custom filters was sending timedelta objects from tempban and shadowban filters to a string converter because of an oversight when switching to fetch them from the already parsed custom filters in memory instead of fetching them from the database a while back. 2) Tickled the version number.
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.14 change log: 1) Commented out all error logging and timeout handling from the database script. • It's not needed anymore. The timeouts were caused by modification contexts not being equipped to handle key errors because some decorators were rewritten to cut back on dB calls and while their fallbacks expected users to sometimes not exist, when that's tripped under aenter it doesn't aexit. It was …
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.13 change log: 1) Added a cache prop for staff IDs when staff create system messages using 'say' commands or their admin chat topic. 2) Removed an unused variable from the internal cache ID assignment thingy. 3) Staff can now edit their own 'say' commands by editing the message they used to send it to change what the message says instead of having to delete the old one and send a new one to fix it.…
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.12 change log: 1) Corrected an oversight that allowed custom filter phrases to be duplicated if the case didn't exactly match. • The case is normalized for triggers, so this could cause some confusing behavior with multiple punishment types assigned to the same phrase chosen at random. 2) Custom filter entries that are duplicates with mixed cases will be deleted when a bot starts, leaving only th…
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.112 change log: 1) Fixed an error where a typo could cause queue priority to be set to None instead of an integer when sending media groups to a bot's relay group. 2) Tickled the version number.
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.111 change log: 1) Fixed a goofy error where inline queries were trying to fetch a chat ID instead of using the querying user's ID. 2) Fixed another goofy error where inline callbacks for join requests were using the tag regular callbacks used to close them, which didn't belong there and wasn't being watched for. 3) Tickled the version number.
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.11 change log: ⚠️ The queuing process has been heavily overhauled to fix some potential bugs with rate limiting. This version is not compatible with older builds. If you have things queued for some reason, wait for the queues to empty before updating to this version or your bot will not start. 1) Fixed a huge oversight where private admin topic reporting could cancel sending to some recipients if on…
custom 53753271449121280572
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.1 change log: 1) System toggle management has been rewritten to utilize the db modification context everything else uses. • Instead of overwriting ~80 rows every time a toggle is pressed, it now seeks the specific toggle and only touches that. 2) Added inputmedia support for links. 3) Polls can now contain link objects. 4) Updated the bot API to 10.1. 5) The number of characters in text no lon…
custom 53753271449121280573
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.09 change log: 1) Added a display name variable that's kept in memory. • It is fetched when a bot starts to name unnamed chats. Now it is also stored, but it doesn't need to be permanent since it would duplicate the bot name system config in most cases. The bot name can be edited in the admin panel, but this one is meant to always match the bot's actual name. 2) When multiple Covert Cove bots are…
custom 53753271449121280574
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.082 change log: 1) Fixed an error where tempbans and yeets were running their staff member target verifications incorrectly. 2) Tickled the version number.
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.081 change log: 1) If an instance's bot is swapped for another, retrieving the staff list will no longer fail. 2) Modified the dB exit method. 3) Fixed an error where reaction downvotes bound to custom emojis were being interpreted as upvotes. 2) Tickled the version number.
Signed ニブル・雪豹 （グレーストライプ）
Covert Cove v61.08 change log: 1) Deleted system messages are logged correctly when the system message is media without a caption. 2) Public log messages show in an admin's public log topic in the bot's private chat when the same log type is excluded from private logs. 3) If a topic in a bot's private chat is left unassigned for 45 seconds, it will be deleted. 4) Added a setting to the user settings panel that al…
Signed ニブル・雪豹 （グレーストライプ）
Showing the 12 most recent of 20 posts we hold for @covertcove. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“CovertCove Updates” (@covertcove), 775 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/covertcove.
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.