Telegram RegisterThe public register of Telegram
Telegram profile photo for SHINY─𝐆 𝐎 𝐋 𝐃 ᴰʳᵉˢˢ

Channel

SHINY─𝐆 𝐎 𝐋 𝐃 ᴰʳᵉˢˢ

@V_iStrategic

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002928798447
TypeChannel
Username@V_iStrategic
DescriptionBasillisa • • not merely a títlos, but a symbol of níke. She is the shadow of an ancient Basileus of Greece, dwelling between mythos and historía. 𝗚𝗮𝗹𝗲𝗿𝗶𝗮 ─ @onoma_a 𝗖𝗿𝗼𝘄𝗻 ─ @V_iStrategic 𝗢𝘁𝗵𝗲𝗿 𝘀𝗶𝗱𝗲 ─ @pneuma_a
CreatedBetween 1 August 2025 and 23 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live11 September 2026
Measurements held2
On Telegramt.me/V_iStrategic

Growth

112 August 2026 — 1 subscribers14 August 2026 — 1 subscribers12 August 202614 August 2026
2 measurements spanning 2 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:021no change
12 Aug 2026, 12:021first reading

Engagement

19 posts held, back to 23 August 2025 — 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 19 posts for this entry, the most recent from 24 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Links
1

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

27 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5764869872521581153829.6%
custom 5215327827745839526518.5%
custom 6203970153290403938518.5%
custom 5215324073944423501414.8%
custom 6154631201081527448414.8%
custom 540659119970217268313.70%

Custom emoji. Every row above is a 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 are Telegram’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 7 of the 19 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 23 August 2025 to 24 August 2025, 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

24 Aug 2025, 05:22 UTCviews —

Channel name was changed to «ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ»

23 Aug 2025, 17:41 UTC137 views4 reactionsread 14 August 2026

🫀

custom 52153278277458395263custom 52153240739444235011

23 Aug 2025, 17:40 UTC132 views5 reactionsread 14 August 2026
Photo

「𝙈y Love」━ 𝓐𝗹𝘄𝗮𝘆𝘀 𝓣𝗼𝗴𝗲𝘁𝗵𝗲𝗿 𝓦𝗶𝘁𝗵 𝓗𝗶𝗺. (@coo_lBoy) 𝙅ourney ━ 𝓛𝗼𝘃𝗲 𝓕𝗮𝗶𝗹𝘂𝗿𝗲𝘀 𝓐𝗻𝗱 𝓢𝘂𝗰𝗰𝗲𝘀𝘀𝗲𝘀 𝙐ntil 𝖭𝗈𝗐 ━ 𝟮𝟬𝟮𝟯...𝘁𝗼...𝟮𝟬𝟮𝟱 (Shazhya X Kenzo) "SnK" couple who experienced many obstacles but still together until now ❤️ In the palace of my heart, you reign supreme, a sovereign of light, my eternal dream. Every glance from your eyes …

custom 52153240739444235013custom 52153278277458395262

23 Aug 2025, 16:45 UTC99 views5 reactionsread 14 August 2026

😇

custom 61546312010815274483custom 57648698725215811532

23 Aug 2025, 16:38 UTC94 views5 reactionsread 14 August 2026

˒ ✨𝐑𝐎𝐘𝐀𝐋 𝐅𝐀𝐌𝐈𝐋𝐘 𝐋𝐈𝐅𝐄 𝐈𝐈𝐈✨ 𝐁𝐈𝐆 𝐍𝐀𝐌𝐄 .... 𝐌𝐀𝐆𝐍𝐈𝐅𝐈𝐂𝐄𝐍𝐓 ╸𝐓he life of @V_iStrategic, which is full of riches ╸𝐑oyal Ambience ╸𝐁eauty, prosperity and welfare 👑━━ 𝐏𝐀𝐆𝐄 𝐈 : Life In The Kingdom Behind the megalē gates and towering spires, life pulses like the eternal rhythm of the palace. Every step in the marmaros hall, every whisper in the corridors, is a fragment of the stories…

custom 57648698725215811534custom 54065911997021726831

23 Aug 2025, 16:37 UTC69 views4 reactionsread 14 August 2026

˒ ˒ ˓

custom 62039701532904039383custom 61546312010815274481

23 Aug 2025, 15:34 UTCviews —

Channel name was changed to «SHINY─𝐆 𝐎 𝐋 𝐃 ᴰʳᵉˢˢ»

Showing the 12 most recent of 19 posts we hold for @V_iStrategic. 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.

Mentions

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.

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

“SHINY─𝐆 𝐎 𝐋 𝐃 ᴰʳᵉˢˢ” (@V_iStrategic), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/V_iStrategic.

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.