Messages in this channel will be automatically deleted after 1 day

Channel
Курс Kingy
@kurskingy
On this record: Growth · Engagement · Posts · Cite this entry
248subscribers
-3 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 | -1002047732871 |
|---|---|
| Type | Channel |
| Username | @kurskingy |
| Created | Between 1 November 2023 and 8 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/kurskingy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 03:06 | 248 | -2 |
| 23 Aug 2026, 17:56 | 250 | +1 |
| 15 Aug 2026, 07:17 | 249 | -2 |
| 8 Aug 2026, 09:30 | 251 | no change |
| 7 Aug 2026, 12:07 | 251 | first reading |
Engagement
20 posts held, back to 8 April 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 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 20 posts for this entry, the most recent from 17 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
🦘🦘🦘 X-Xrocket D-Dedust 00:09 X:⚪0.0169 ton 0% D: 0.02 ton
Курс Kingy pinned Deleted message
🦘🦘🦘 X-Xrocket D-Dedust 02:10 X:⚪0.1 ton 0% D: 0.10 ton
🦘🦘🦘 X-Xrocket D-Dedust 00:10 X:⚪0.101 ton 0% D: 0.10 ton
🦘🦘🦘 X-Xrocket D-Dedust 22:10 X:⚪0.1 ton 0% D: 0.11 ton 23:39 X:🟢0.101 ton ↑0.99% D:0.10 ton
🦘🦘🦘 X-Xrocket D-Dedust 20:10 X:⚪0.107 ton 0% D: 0.11 ton 20:42 X:🔴0.104 ton ↓-2.88% D:0.11 ton 20:56 X:🔴0.100 ton ↓-4.00% D:0.11 ton 21:32 X:🔴0.100 ton ↓-1.00% D:0.11 ton
🦘🦘🦘 X-Xrocket D-Dedust 18:10 X:⚪0.108 ton 0% D: 0.11 ton 18:16 X:🔴0.107 ton ↓-0.93% D:0.11 ton
🦘🦘🦘 X-Xrocket D-Dedust 16:10 X:⚪0.106 ton 0% D: 0.11 ton 17:01 X:🔴0.106 ton ↓-0.94% D:0.11 ton 17:08 X:🟢0.114 ton ↑7.02% D:0.11 ton 17:41 X:🟢0.107 ton ↑0.93% D:0.11 ton
🦘🦘🦘 X-Xrocket D-Dedust 14:10 X:⚪0.105 ton 0% D: 0.11 ton 14:21 X:🟢0.106 ton ↑0.94% D:0.11 ton 15:15 X:🟢0.107 ton ↑0.93% D:0.11 ton 15:17 X:🔴0.106 ton ↓-0.94% D:0.11 ton 15:40 X:🟢0.400 ton ↑73.50% D:0.11 ton
🦘🦘🦘 X-Xrocket D-Dedust 12:10 X:⚪0.105 ton 0% D: 0.11 ton 13:13 X:🟢0.106 ton ↑0.94% D:0.11 ton 13:51 X:🟢0.106 ton ↑0.94% D:0.11 ton 14:09 X:🔴0.105 ton ↓-0.95% D:0.11 ton
🦘🦘🦘 X-Xrocket D-Dedust 10:10 X:⚪0.115 ton 0% D: 0.12 ton 10:31 X:🟢0.116 ton ↑0.86% D:0.12 ton 10:51 X:🔴0.115 ton ↓-0.87% D:0.12 ton 11:04 X:🔴0.109 ton ↓-5.50% D:0.11 ton 11:14 X:🟢0.108 ton ↑0.93% D:0.11 ton 11:46 X:🟢0.109 ton ↑0.92% D:0.11 ton 11:48 X:🔴0.108 ton ↓-0.93% D:0.11 ton 11:56 X:🔴0.105 ton ↓-2.86% D:0.11 ton
Showing the 12 most recent of 20 posts we hold for @kurskingy. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Курс Kingy” (@kurskingy), 248 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/kurskingy.
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.