Channel
@arink13
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
1,078subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001544792695 |
|---|---|
| Type | Channel |
| Username | @arink13 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/arink13 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 02:32 | 1,078 | -6 |
| 18 Aug 2026, 00:42 | 1,084 | -1 |
| 14 Aug 2026, 16:28 | 1,085 | -2 |
| 11 Aug 2026, 08:53 | 1,087 | -3 |
| 8 Aug 2026, 00:05 | 1,090 | no change |
| 7 Aug 2026, 23:57 | 1,090 | -2 |
| 7 Aug 2026, 17:03 | 1,092 | first reading |
5 posts held, back to 1 August 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 5 (1 August 2026 – 4 August 2026) |
| Views total | 1,383 |
| Reactions total | 199 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:05 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
199 reactions across 4 posts, in 13 distinct kinds. The most used accounts for 19.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5318842904720989904 | 39 | 19.6% | |
| 💘 | 35 | 17.6% | |
| 🕊 | 30 | 15.1% | |
| 🔥 | 25 | 12.6% | |
| custom 5433973587604163454 | 22 | 11.1% | |
| custom 5337048437865084655 | 16 | 8.04% | |
| custom 5264834816255227491 | 11 | 5.53% | |
| custom 5343744038476477589 | 9 | 4.52% | |
| custom 5334842375158132207 | 3 | 1.51% | |
| custom 5397954291052860678 | 3 | 1.51% | |
| 💔 | 3 | 1.51% | |
| custom 5316787470812075659 | 2 | 1.01% | |
| custom 5357053970328076463 | 1 | 0.503% |
Custom emoji. 9 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 4 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 199reactions 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 1 August 2026 to 4 August 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @arink13. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 5 most recent posts we hold for this entry, published 1 August 2026 to 4 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Начну с место с которого я влюбилась 🧸🥹🦋 Ланчи бранчи! Много очень видела в рилс это место, но не было вообще интереса, один раз зашла туда, и не могла больше не вернутся. Сотрудники все вообще милашки, сервис 10/10, все быстро приносят, и всегда ну оочень вкусно, сытно, красиво🤩🤩
custom 531884290472098990418💘8custom 52648348162552274916🕊1custom 53167874708120756591custom 53437440384764775891custom 54339735876041634541
Завершающий пост думаю уже надо сделать 😇 Еда конечно на природе любая очень вкусная, но на сплаве и вправду все было 10/10! утро каша с ананасами, обед бывал суп, вечер гречки, а в последний день паста. -Исполнение мечты🤩, Очень много вайбовых фотографий с фотика📸, новые крутые знакомства 🤩, Опыт управление веслами 🤩
🔥25custom 53437440384764775898custom 54339735876041634545custom 53979542910528606783💘1custom 53167874708120756591
Kudymchik🤍 pinned a video
Я почти закончила наконец делать все посты со сплава, ну и сам влог 🤩!!!!! ( еще один пост буквально) Заработала тем самым еще минус 15 отписок 🤩🤩🤩 Чуть чуть поднабирется актив, и накочу еще посты за последние время 🫶! Там места Перми распишу, момента классные, и т.д. Очень хочется надеется что я не зря здесь возобновила актив, и как то стараюсь над постами кому то интересно (((
🕊21custom 531884290472098990418custom 533704843786508465514💔3custom 52648348162552274911custom 53348423751581322071
Просто, виды! когда увидеть эти Уральские красивейшие горы было моей мечтой💔 я так кайфовала в моменте когда мы все это проплавали. Впервые в своей жизни я увидела огромного бобра. Был момент, когда мы плыли абсолютно одни несколько часов. Я была уверена, что мы заблудились🌟. Не забуду, как несколько раз плыли и смотрели, наши ли это. Половина пути прошла под громкую музыку, без музыки — с разговорами, и в спокойной…
💘26custom 543397358760416345416🕊8custom 52648348162552274914custom 53188429047209899043custom 53348423751581322072custom 53370484378650846552custom 53570539703280764631
Showing the 5 most recent of 5 posts we hold for @arink13. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 1,025,779 of 1,621,754entries 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.
Named by 1 registered channel — 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.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Kudymchik🤍” (@arink13), 1,078 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/arink13.
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.