Telegram RegisterThe public register of Telegram
Telegram profile photo for LiMKA NFT

Channel

LiMKA NFT

@wi0shkaa

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

485subscribers

-4 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003723716007
TypeChannel
Username@wi0shkaa
Created2 April 2026measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/wi0shkaa

Growth

4854894878 Aug 2026, 09:04 — 489 subscribers9 Aug 2026, 02:11 — 485 subscribers8 Aug 2026, 09:049 Aug 2026, 02:11
2 measurements taken within a single day, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 484–490 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 02:11485-4
8 Aug 2026, 09:04489first reading

Engagement

12 posts held, back to 2 April 2026the 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 12 posts for this entry, the most recent from 6 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

69 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 49.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54382213832743492103449.3%
custom 52808316324025638862637.7%
710.1%
custom 532804601890893580511.45%
💋11.45%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 10 of the 12 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 69reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 2 April 2026 to 6 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Jul 2026, 13:56 UTC219 views1 reactionsread 8 August 2026

2 сердца/ 2 победителя💘 Быть подписанным на https://t.me/Krovi_S8

custom 52808316324025638861

6 Jul 2026, 10:47 UTC247 views10 reactionsread 8 August 2026

Мишка - минутка𖣂 Быть подписанным на @vold_stars

custom 52808316324025638865custom 54382213832743492105

6 Jul 2026, 10:35 UTC254 viewsread 8 August 2026

Минутка - сердце 💘 Быть подписанным на @zvezd_qqq

6 Jul 2026, 09:57 UTC292 views16 reactionsread 8 August 2026

Мишка - минутка𖣂

custom 528083163240256388610custom 54382213832743492106

5 Jul 2026, 19:22 UTC315 views5 reactionsread 8 August 2026

Мишка - минутка 𖣂 Быть подписанным на @zvezd_okk

custom 54382213832743492103custom 52808316324025638862

5 Jul 2026, 19:02 UTC309 views7 reactionsread 8 August 2026

Сердешко - минутка💘

custom 54382213832743492104custom 52808316324025638863

4 Jul 2026, 18:13 UTC305 views2 reactionsread 8 August 2026

Мишка - минутка⭐️

custom 52808316324025638862

4 Jul 2026, 17:41 UTC295 views11 reactionsread 8 August 2026

Мишка - минутка

custom 543822138327434921011

3 Jul 2026, 17:51 UTC286 views6 reactionsread 8 August 2026

Сердечко - минутка

custom 52808316324025638863custom 54382213832743492103

3 Jul 2026, 17:23 UTC308 views2 reactionsread 8 August 2026

Мишка - минутка

💋1custom 53280460189089358051

2 Jul 2026, 17:24 UTC358 views9 reactionsread 8 August 2026
Video

ВКЛЮЧИТЕ УВЕДОМЛЕНИЯ:: ⚜️чтобы не пропускать раздачи и конкурсы ПРАВИЛА ЧТОБЫ ПОЛУЧИТЬ ПРИЗ:: быть в чате https://t.me/wi0shkaaaaaa на отписку в лс 1 мин быть подписанным на данный канал

7custom 54382213832743492102

Showing the 12 most recent of 12 posts we hold for @wi0shkaa. 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 — 536,161 of 1,481,217entries 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.

Forward network

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.

Mentions

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“LiMKA NFT” (@wi0shkaa), 485 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/wi0shkaa.

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.