Channel
@YukkiStore
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
237subscribers
-9 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001781810312 |
|---|---|
| Type | Channel |
| Username | @YukkiStore |
| Created | 2 April 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/YukkiStore |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 12:15 | 237 | -3 |
| 2 Sept 2026, 14:56 | 240 | -1 |
| 27 Aug 2026, 12:36 | 241 | -2 |
| 20 Aug 2026, 00:47 | 243 | -1 |
| 13 Aug 2026, 12:46 | 244 | -2 |
| 7 Aug 2026, 02:31 | 246 | no change |
| 6 Aug 2026, 20:46 | 246 | first reading |
4 posts held, back to 2 April 2022 — 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 page of 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 4 posts for this entry, the most recent from 27 August 2022. An engagement rate over an empty window would be a number about nothing.
💡Yukki Store presents cloud services sales , get best services in whole market with us at affordable prices. Dm @YukkiAdvertising to buy ! 📌 VPS: • Available Cpu Sizes : 2 core / 4 core / 8 cores • Ram upto 64GB • Storage Upto 500 GB • Working Period : 25 Days 📌 RDP ( 25 port open ) : • Available Sizes : 4 gb / 8 gb / 16 gb • Anti Ban RDP's • Working Period : 15 Days 📌 Close port RDP: • Available Sizes : 8gb / 16…
Shop/Store Bot with Integrated Payment Gateway and SQL panel. • Accept Payments in your bank account directly from telegram with upi , wallets and cards. • Auto verifying payment , instant item deliver on payment / no waiting time • MyPhpAdmin Panel / SQL Connected • WebApp Interactive UI • Seperate Admin Panel for user management and broadcasting messages. Test Bot :- @ShuklaSonsBot Purchase Bot / Source :- @Shik…
A complete solution to your demand and ideas. Get custom bots , projects , smm panels, websites , payment gateway integrated , source codes and many more thing made with Team Yukki. Team Yukki consists of many devs from different region knowing different languages. We’ll get your projects working within time and in proper manner. For more queries: @Shikhar Join @YukkiStore Join @YukkiStore Join @YukkiStore
Channel created
Showing the 4 most recent of 4 posts we hold for @YukkiStore. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 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.
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.
@YukkiStore named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Yukki Store” (@YukkiStore), 237 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/YukkiStore.
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.