Channel
@kotatogram
On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry
1,831subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001397627823 |
|---|---|
| Type | Channel |
| Username | @kotatogram |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/kotatogram |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:02 | 1,831 | -6 |
| 9 Aug 2026, 08:51 | 1,837 | +3 |
| 6 Aug 2026, 15:17 | 1,834 | no change |
| 6 Aug 2026, 14:47 | 1,834 | first reading |
10 posts held, back to 31 December 2021 — 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 10 posts for this entry, the most recent from 2 January 2024. An engagement rate over an empty window would be a number about nothing.
New test build and and new development blogs channel I've thought about how to do it properly and decided that short summaries will be posted here, and most development posts will be in separate channel. So the first thing is, here is new channel: https://t.me/kotatogram_dev I've started with attempt to update patches-track-4.8.4 branch to 4.14. Suprisingly, it took less time than I expected, so I've built the new…
What is better for development blogs?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
About Kotatogram's state The silence has been gone too long, and with it more people asking in comments, why, or some even consider the app dead. So I'm telling it once again: Kotatogram isn't dead. I don't have enough time for it, but there's a progress. Since I was tired of countless merge conflicts, I've made patches-track branch. This is an additional branch, where each change stored in separate commit instead…
Since Telegram massively revokes usernames of channels considered inactive by them, here is the notice: Kotatogram isn't dead, update will be soon.
New version is out! 1.4.9 (TD 3.5.2) Changes • Internal rework of Kotatogram Settings. • Restart to save settings now can be delayed. • Select time when jumping to date in chat. • Experimental settings from Telegram Desktop now are always shown. • Name icon colors are now same as name colors. • Fixed profile picture cropping in native Windows notifications. • "Emoji panel by hover" option replaced by default one. • …
#Linux
#WindowsInstaller
New version is out! 1.4.8 (TD 3.3) This release is unexpected, but important because of severe crash in Saved Messages. If you haven't caught it, you're in luck, but it's better to update anyway. Changes • Better font settings. Thanks to the @Shlyupa's work, there is now a full list of fonts after an each font name field, and also there is a slider to change font size. Earlier font size could be changed only throug…
#Linux
New version is out! 1.4.7 (TD 3.3) Last release in this year which is needed because who knows what happen if stable branch won't receive update until January 1. Luckily, the "make it before January 1" thing is not the only point of the release: new features are also in stock. Changes since last beta version • Instead of removing window size restiction minimum window size was changed. It solves the same problem, bu…
Showing the 10 most recent of 10 posts we hold for @kotatogram. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
What is better for development blogs?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 10 most recent posts we hold, published 31 December 2021 to 2 January 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 763,647 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.
Named by 3 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Kotatogram” (@kotatogram), 1,831 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kotatogram.
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.