А я вам лову на ос 💔
custom 53008038788690219572❤1
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡

Channel
@BEIIA228
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
411subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003730204045 |
|---|---|
| Type | Channel |
| Username | @BEIIA228 |
| Description | ꢒρμɞετ ӄμϲγϰꤎ 🍷? «Ορμӷμϰαλƅϰƅɩύ ӄαϰαλ: ϰετ ӄσημρσӄ» 💋 Λϲ @KOTN_MRY_MRY Менеджер: @monahk228 / @Likycu Хештег/ #бэл #Б #торт Навигация : @BellaandLikycu |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BEIIA228 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 02:15 | 411 | no change |
| 10 Aug 2026, 02:03 | 411 | first reading |
17 posts held, back to 2 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 9 August 2026 |
|---|---|
| Posts held | 17 (2 August 2026 – 9 August 2026) |
| Views total | 2,202 |
| Reactions total | 304 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 02:15 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.
Lifetime counters from Telegram’s own channel header, read 10 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.
304 reactions across 17 posts, in 22 distinct kinds. The most used accounts for 18.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5330271928659779224 | 56 | 18.4% | |
| custom 5433693431182420289 | 33 | 10.9% | |
| custom 5330480097134688390 | 28 | 9.21% | |
| custom 5425049719304904578 | 27 | 8.88% | |
| custom 5411218649006494983 | 20 | 6.58% | |
| custom 5357461558429523605 | 19 | 6.25% | |
| custom 5906971253511561081 | 19 | 6.25% | |
| custom 5906810553015213665 | 12 | 3.95% | |
| 💘 | 12 | 3.95% | |
| custom 5264761320774867677 | 11 | 3.62% | |
| custom 5395849387710630005 | 10 | 3.29% | |
| custom 5445205163306410132 | 8 | 2.63% | |
| custom 6019357611206382760 | 8 | 2.63% | |
| custom 5300803878869021957 | 7 | 2.30% | |
| custom 6019163405670159872 | 7 | 2.30% | |
| custom 5469670937701949321 | 6 | 1.97% | |
| ❤ | 6 | 1.97% | |
| custom 6019295085072487516 | 5 | 1.64% | |
| custom 5298961952079360362 | 3 | 0.987% | |
| 💯 | 3 | 0.987% | |
| 2 further kinds | 4 | 1.32% |
Custom emoji. 17 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 17 of the 17 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 304reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 2 August 2026 to 9 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.
А я вам лову на ос 💔
custom 53008038788690219572❤1
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
https://t.me/boost/BEIIA228 Дайте чуток 😫
custom 54336934311824202895💯1custom 53958493877106300051
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Накидайте игр Думаю или сегодня ближе через час поиграем или же уже завтра на утречко.
❤4custom 54112186490064949832custom 54336934311824202892
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Хорошо ,мои хорошие. В вышибалы будем? Или в ассоциацию? Накидайте игр а там дальше уже решим
custom 54696709377019493216custom 54336934311824202895custom 54112186490064949832❤1
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Posted without readable text
💯2custom 53008038788690219572custom 53958493877106300051
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Пуп
custom 541121864900649498311custom 53008038788690219573custom 60193576112063827603
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
-🍒] ну или комфортен: на ваш вкус)
custom 543369343118242028918custom 53958493877106300058custom 54452051633064101327❤🔥2custom 52989619520793603621custom 54112186490064949831
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
-🍒] напомню о аукционе. «Чуть ниже еще второй»
custom 60193576112063827605custom 52989619520793603622custom 54336934311824202891
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
❤️🤍авигация.💄'» ִׄ𝆹𝅥 𝅄 ִ — В этой группе есть все материалы которые вам могут пригодиться. •Всё о новых адоптах — ссылки на адопты, мои сот.сети. Все это именно вы можете найти там. 𖥻 ْ 𓈒 ·𝑡𝑒𝑔𝑠::#навигация.#пост.
custom 60191634056701598727custom 60192950850724875165custom 52603106480294812792custom 54112186490064949831custom 54336934311824202891
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
ྀིྀི ─✦- ྀིྀི ⋆⋅·✦·⋅⋆ ྀིྀི -—⋆⋅·✦ ྀིྀི — 🪭🔤🔤🔤🔤❤️ - наконец-то оконченный арт над которым думала судки. Мне личико нрав (я знаю вы уже видели это на аве. Но не всю работу же) 🩸🔤🔤🔤🔤🔤🔤🔤🔤 -буду рада комментариям «Юз:KOTN_MRY_MRY🫦 🫦: анонимка: #BэlLa #арт #пост
custom 53574615584295236059custom 53304800971346883904custom 54250497193049045783custom 53302719286597792242custom 54336934311824202891custom 54452051633064101321
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Давайте по больше реакций
custom 53302719286597792246custom 54250497193049045786custom 59068105530152136654custom 59069712535115610813
Signed 𝐿𝑖𝑘𝑦𝑐𝑢.⁸
•🤩🤩🤩🤩🎁» . 🍓🤩🤩🤩🤩🤩🤩🤩› — 🔤от и новый пак подъехал, более пастельный и миленький. Больше пока адоптов чиби не будет, но будет кое-что по круче. Надеюсь и эти и прошлые вы быстренько раскупите.🕷 За покупочкой – @KOTN_MRY_MRY . «Анонимка» (Буду рада вашему комментарию) ·𝑡𝑒𝑔𝑠::#BэlLa.#аук.#пост.🕷ִׄ𝆹𝅥 𝅄 ִ
custom 533027192865977922412💘3custom 53304800971346883903custom 53574615584295236053custom 52647613207748676772custom 54112186490064949832custom 59068105530152136652custom 59069712535115610811
Signed ʚ𑣲𐌱϶𐍰𐍰𐌳♡
Showing the 12 most recent of 17 posts we hold for @BEIIA228. 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 — 371,905 of 1,189,255entries 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.
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.
Named by 3 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“ʚ𑣲芸術,𐌱϶𐍰𐍰𐌳♡ɞ*🍷” (@BEIIA228), 411 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BEIIA228.
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.