Channel
@biads228
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
20subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002384912218 |
|---|---|
| Type | Channel |
| Username | @biads228 |
| Description | Мой тгк,я из лайка под ником ,,Biser228🦁’’ подписывайся тут будет много контента) |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/biads228 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:15 | 20 | no change |
| 12 Aug 2026, 02:03 | 20 | first reading |
18 posts held, back to 14 May 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 pageof 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 18 posts for this entry, the most recent from 12 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
42 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 40.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 40.5% | |
| 💘 | 9 | 21.4% | |
| 🔥 | 7 | 16.7% | |
| 🥰 | 4 | 9.52% | |
| 😁 | 3 | 7.14% | |
| 🤯 | 2 | 4.76% |
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 18 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 42reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 14 May 2025 to 12 October 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.
🐻Набор в тест на хелпи!🐻 Условия : 1.подписка на мой тгк: @fnaf98ooo 2.переслать на канал 10+ под. 3.скинуть свои работы 4.скрины первых двух пунктов Анкета: 1. Скинуть работы 2.успеешь в срок? Срок : 15-17 дней включительно(или же до 29-30 октября), можете попросить удленить срок на 1 день Схема будет готова примерно в течении 5 дней , голова уже готова Отбор будет 14-15 октября 🎏
💘1
•Набор в тест на корги =================== •Условия: •Подписка на @CuteBeadsUA24 •Пересыл на основной канал 2+ / либо 2 друзьям •Прислать 5-6 работ, либо колаж (огромный не нужно) =================== •Анкета: •Кидая анкету вы соглашаетесь что: °Успеете в срок месяц °Понимаете схемы, не будет писать в лс за каждой меткой °Подождёте схему °Есть нужные материалы •Для подтверждения пишите "согласна / согласен " =========…
Немного бисера
🔥2🤯2
Ну короче как то так дела в поезде обстоят
🔥1
Ну и постик с процессом,и что я возьму с собой к бабушке,сплела я это за 5 дней,учитывая то что три из них я работала☺️ Думаю это хороший результат💗
❤2
Пост с грангильдой!🔥🔥 Плела я ее долго из за того что забрасывала ее,могу сказать что плести её легко,но крылья это отдельный вид искусство 🤨 Плела её на тест от Тани,и я была этому очень рада,на этом всё,щас будет постик с процессом❤️❤️
❤2
Сегодня без новой ами(мне было лень фоткать),но зато,постаралась в максимум поплести после работы(я плела с большими перерывами) На этом всё,всем спокее❤️🔥❤️
❤3
Сегодня пост! Ну и немного процесика новой работки🤩❤️
❤2
Photo, posted without a caption
❤1
Спустя 100 лет пост,и да завтра постараюсь доделать эту ами!❤️
❤2🔥2🥰2
Небольшие подарки себе🌟❤️
😁3🔥2🥰2💘1
Хоп Нанинай)
❤2
Showing the 12 most recent of 18 posts we hold for @biads228. 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 — 1,128,599 of 1,169,250entries 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.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Biser228🦁” (@biads228), 20 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/biads228.
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.