Video, posted without a caption
custom 53144471817871913302custom 53548529413227993631custom 53661212175205838941

Channel
@yotura_na_flike
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
122subscribers
-19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002858494238 |
|---|---|
| Type | Channel |
| Username | @yotura_na_flike |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/yotura_na_flike |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 08:20 | 122 | -9 |
| 4 Sept 2026, 11:39 | 131 | -7 |
| 28 Aug 2026, 09:02 | 138 | -12 |
| 21 Aug 2026, 05:47 | 150 | +10 |
| 14 Aug 2026, 11:58 | 140 | -1 |
| 8 Aug 2026, 22:02 | 141 | no change |
| 6 Aug 2026, 23:18 | 141 | first reading |
20 posts held, back to 15 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 20 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 15 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.
74 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 21.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5354852941322799363 | 16 | 21.6% | |
| custom 5366121217520583894 | 16 | 21.6% | |
| custom 5462871046694651149 | 10 | 13.5% | |
| custom 5330336443363530677 | 9 | 12.2% | |
| custom 5314447181787191330 | 8 | 10.8% | |
| custom 5415913804175266877 | 8 | 10.8% | |
| custom 6219549292458150316 | 6 | 8.11% | |
| custom 5276477287183687194 | 1 | 1.35% |
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 17 of the 20 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 74 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 15 July 2026 to 29 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.
Video, posted without a caption
custom 53144471817871913302custom 53548529413227993631custom 53661212175205838941
Тур проход Vs какой-то silver
custom 62195492924581503162custom 53303364433635306771custom 54159138041752668771
Video, posted without a caption
custom 53548529413227993633custom 53661212175205838941custom 54628710466946511491
Вот еще пруф насчет реги)
Жаль не 3 За регой в лс @kofub
Накиньте реакций чтоль 🇷🇺
custom 53548529413227993631custom 62195492924581503161
Тур проход Vs какой то V1rtu3
custom 53548529413227993635custom 53303364433635306773custom 62195492924581503162custom 53661212175205838941
Платка. 1 игра за два дня, и все таки не удачно , вообще не летный день сегодня
custom 53661212175205838942custom 53303364433635306771custom 54628710466946511491
Video, posted without a caption
custom 54628710466946511494custom 53661212175205838941custom 54159138041752668771
Video, posted without a caption
custom 53548529413227993633custom 53303364433635306771custom 54159138041752668771
Чет давно моментов не клипал
XD
custom 53661212175205838941custom 54159138041752668771custom 62195492924581503161
Showing the 12 most recent of 20 posts we hold for @yotura_na_flike. 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@yotura_na_flike 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“В гостях у Yotura” (@yotura_na_flike), 122 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/yotura_na_flike.
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.