Posted without readable text
custom 543624542773526230719custom 53844957275629896089custom 53280630441592899437custom 53819118194031608982

Channel
@vikltt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
101subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001680482108 |
|---|---|
| Type | Channel |
| Username | @vikltt |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/vikltt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:33 | 101 | -1 |
| 9 Aug 2026, 10:02 | 102 | no change |
| 7 Aug 2026, 19:15 | 102 | first reading |
5 posts held, back to 5 July 2026 — 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 5 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
149 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 24.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5269307775585907020 | 37 | 24.8% | |
| custom 5325872881421273066 | 25 | 16.8% | |
| custom 5328063044159289943 | 24 | 16.1% | |
| custom 5381911819403160898 | 22 | 14.8% | |
| custom 5384495727562989608 | 22 | 14.8% | |
| custom 5436245427735262307 | 19 | 12.8% |
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 5 of the 5 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 149 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 5 July 2026 to 26 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.
Posted without readable text
custom 543624542773526230719custom 53844957275629896089custom 53280630441592899437custom 53819118194031608982
Photo, posted without a caption
custom 538191181940316089811custom 52693077755859070207custom 53844957275629896086custom 53280630441592899432
🪽
custom 532587288142127306611custom 52693077755859070207custom 53280630441592899435
3 дня на Ладожском 🌅🏕️
custom 526930777558590702014custom 53819118194031608989custom 53844957275629896087
✌❤️🤳
custom 532587288142127306614custom 532806304415928994310custom 52693077755859070209
Showing the 5 most recent of 5 posts we hold for @vikltt. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
“vikllt” (@vikltt), 101 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/vikltt.
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.