6 Mar 2025, 20:48 UTC≈1,670 viewsread 7 August 2026
Робота сервісу відновлена. The service has been restored.
Channel
Kuna status
@kunastatus
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,647subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001271234317 |
|---|---|
| Type | Channel |
| Username | @kunastatus |
| 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/kunastatus |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:56 | 1,647 | -1 |
| 9 Aug 2026, 12:41 | 1,648 | -3 |
| 6 Aug 2026, 07:19 | 1,651 | no change |
| 6 Aug 2026, 05:04 | 1,651 | first reading |
Engagement
20 posts held, back to 22 October 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 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 6 March 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
5 Mar 2025, 10:56 UTC≈1,880 viewsread 7 August 2026
06 Березня о 21:00 (UTC+1) заплановані технічні роботи. Орієнтовний час проведення дві години. Введення / виведення криптовалютних та фіатних активів, торги, API, будуть недоступні. Прохання враховувати дану інформацію при роботі з платформою.
14 Jan 2025, 15:22 UTC≈3,330 viewsread 7 August 2026
Робота сервісу відновлена. The service has been restored.
14 Jan 2025, 15:05 UTC≈3,210 viewsread 7 August 2026
Спостерігаємо тимчасові труднощі та затримку в роботі куна код боту. Проблема з затримкою бота пов'язана з технічною проблемою на стороні сервісу телеграм. We are experiencing temporary difficulties and delays in the work of the code bot. The problem with the delay of the bot is related to a technical problem on the side of the Telegram service.
8 Jan 2025, 15:59 UTC≈3,230 viewsread 7 August 2026
Робота сервісу відновлена. The service has been restored.
8 Jan 2025, 13:38 UTC≈2,880 viewsread 7 August 2026
Проводяться позапланові технічні роботи. Спостерігаються тимчасові труднощі в роботі сервісу. Займаємося вирішенням. Unscheduled technical work is being carried out. Temporary difficulties in service operations. We are working on a solution.
7 Jan 2025, 15:02 UTC≈2,390 viewsread 7 August 2026
Робота сервісу відновлена. The service has been restored.
7 Jan 2025, 14:06 UTC≈2,200 viewsread 7 August 2026
Проводяться позапланові технічні роботи. Спостерігаються тимчасові труднощі в роботі сервісу. Займаємося вирішенням. Unscheduled technical work is being carried out. Temporary difficulties in service operations. We are working on a solution.
28 Nov 2024, 20:19 UTC≈4,720 viewsread 7 August 2026
Робота сервісу відновлена. The service has been restored.
28 Nov 2024, 20:05 UTC≈2,560 viewsread 7 August 2026
Технічні роботи продовжено на 15 хвилин. Maintenance work has been extended by 15 minutes.
28 Nov 2024, 18:55 UTC≈5,580 viewsread 7 August 2026
Шановні користувачі, нагадуємо, що через 5 хвилин розпочинаються технічні роботи. Dear users, we remind you that after 5 minutes technical work will begin.
28 Nov 2024, 13:22 UTC≈5,220 viewsread 7 August 2026
28 Листопада о 20:00 (UTC+1) заплановані технічні роботи. Орієнтовний час проведення одна година. Введення / виведення криптовалютних та фіатних активів, торги, API, та Kuna Code Bot будуть недоступні. Прохання враховувати дану інформацію при роботі з платформою. On 28 November at 20:00 (UTC+1), technical work is scheduled. The estimated time to complete the work is one hour. Deposit / withdrawal of cryptocurrency a…
Showing the 12 most recent of 20 posts we hold for @kunastatus. 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
Citation-graph rank — 914,232 of 1,350,102entries 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.
Mentions
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.
Cite this entry
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.
“Kuna status” (@kunastatus), 1,647 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/kunastatus.
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.