27 Jun 2024, 18:45 UTC151 viewsread 10 August 2026
KIP #6: Increasing the Maximum Cap of KUS Tokens https://snapshot.org/#/kusgov.eth/proposal/0x494b19eef9e1d4ed950374ee4023b66901a4241f1c2538a930a035ba819ab0fb
Channel
KUSGov - KuSwap Core DAO Announcements
@kusgov
On this record: Growth · Engagement · Posts · Cite this entry
35subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001607319383 |
|---|---|
| Type | Channel |
| Username | @kusgov |
| Created | 3 December 2021 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/kusgov |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 01:32 | 35 | -1 |
| 10 Aug 2026, 22:30 | 36 | no change |
| 7 Aug 2026, 05:14 | 36 | first reading |
Engagement
9 posts held, back to 3 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 1 pageof 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 9 posts for this entry, the most recent from 27 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
8 Jun 2023, 14:05 UTC938 viewsread 10 August 2026
KIP #4: Advancing KuSwap with v3 - A Comprehensive Proposal (Part 1) https://snapshot.org/#/kusgov.eth/proposal/0x1625d89a00ee9ed3c85a72b453c52edbc4dceb396bd6339ca90515e288158214
1 Dec 2022, 18:01 UTC≈1,430 viewsread 10 August 2026
KIP #3 - KuSwap v3 Burn Proposal https://snapshot.org/#/kusgov.eth/proposal/0xe2a1a89d9f8b2d188a8f391a6e882bf8add5e4476bb1189c8b9ad76f61e219d6
2 Jul 2022, 18:50 UTC≈1,750 viewsread 10 August 2026
KIP #2 - Anniversary Burn Proposal https://snapshot.org/#/kusgov.eth/proposal/0xb4e56e1287f5acc93a4dd1fac110cf704b342ccf3278f270478e3a2e72af3667
20 Apr 2022, 18:35 UTC≈2,670 viewsread 10 August 2026
🗳 Vote and help us decide the next KuStack pools 🥳 https://snapshot.org/#/kusgov.eth/proposal/0xcc95a2b084b2ec50596dc9bbd43406dc896827b7a53f98a82926ffb67ee51355
11 Mar 2022, 06:21 UTC≈1,580 viewsread 10 August 2026
KIP #1 - Quarterly Burn Proposal Voting starts in 40 mins: https://snapshot.org/#/kusgov.eth/proposal/0x927f3aa6d1bccb41d562f4ea72d99bab740e67339a8f051626865288fe5b5bee
10 Mar 2022, 18:00 UTC≈1,950 viewsread 10 August 2026
#1 Community NFT Proposal VOTE with KUSGov: https://snapshot.org/#/kusgov.eth/proposal/0x33823a585be4d5020cc7fe85c837bc981de08c7d4780e784c97e381defd991af
3 Dec 2021, 17:10 UTCviews —
Channel photo updated
3 Dec 2021, 17:10 UTCviews —
Channel created
Showing the 9 most recent of 9 posts we hold for @kusgov. 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“KUSGov - KuSwap Core DAO Announcements” (@kusgov), 35 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/kusgov.
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.