Telegram RegisterThe public register of Telegram

Channel

Байчик🎙️

@baiichik

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

27subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001593827014
TypeChannel
Username@baiichik
DescriptionОбычный парень, который делится своим мнением, а.к.а душнила. Конь 🔴🔵 VK- https://vk.com/classik890 IG - https://www.instagram.com/zheka12bai?igsh=eDd6NHE0ZjY2eG15
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/baiichik

Growth

277 August 2026 — 27 subscribers11 August 2026 — 27 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 07:0127no change
7 Aug 2026, 07:4527first reading

Engagement

20 posts held, back to 17 May 2026the 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 20 posts for this entry, the most recent from 20 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
186
Videos
80
Links
191

Lifetime counters from Telegram’s own channel header, read 11 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.

Video runtime
7s
Average length
7s

Measured directly from 1 video 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.

Reaction mix

82 reactions across 20 posts, in 19 distinct kinds. The most used accounts for 15.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤝1315.9%
😢911.0%
🤡78.54%
67.32%
👀56.10%
👍56.10%
🔥56.10%
🥱56.10%
👎44.88%
💩44.88%
😭44.88%
custom 519538269540792156933.66%
custom 530999771592763149333.66%
💔22.44%
😨22.44%
🤨22.44%
11.22%
🏆11.22%
🤔11.22%

Custom emoji. 2 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 20 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 82reactions 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 17 May 2026 to 20 June 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.

Recent posts

20 Jun 2026, 20:54 UTC31 views5 reactionsread 11 August 2026

Обидно за Спиритов. Могли выходить в финал.

😢2😨2👀1

19 Jun 2026, 18:52 UTC34 views4 reactionsread 11 August 2026

Если на ЧМ будет что-то лучше матча Спиритов и Г2, то можете праздновать всем селом и открывать шампанское. Я очень давно с таким интересом и вовлеченностью не смотрел что-то кроме ногомяча. Но последние пару дней посмотрел пару-тройку видосов у Рейза и чет заинтересовало. И жалко, что этот момент не закончил игру, было бы мега эпично. Хотя и так это мега эпично. Граффити.

🤝21🔥1

17 Jun 2026, 18:48 UTC26 views4 reactionsread 11 August 2026

Мои симпатии к Португалии улетучились независимо от того, как закончится матч.

😭2🤝1😢1

17 Jun 2026, 17:52 UTC26 views4 reactionsread 11 August 2026

И еще одна галимая вата, но уже от Португалии. И снова просто перекат мяча. Все. И заслуженный гол Конго. Они в атаке гораздо интереснее, чем эти мешки из Португалии.

👎2😢1😭1

16 Jun 2026, 19:58 UTC26 views4 reactionsread 11 August 2026

Франция сейчас похожа на Бразилию. Только бразильцы перестали играть в футбол в середине второго тайма. Франция же перестала играть в футбол в самом начале первого. Очень тухлая игра. Не такого ждешь от главных фаворитов чемпионата. Вообще, почти все большие европейские сборные играют серо и уныло. Как будто акклиматизация идет у них или что. Короче, Франция – тухлятина, похлеще Бразилии и тем более даже такой Испан

💩2👎1😢1

15 Jun 2026, 18:01 UTC20 views4 reactionsread 11 August 2026

Испания это смех, конечно. Все такой же уродский скучный футбол, тупо катание мяча поперек. Но не удивлюсь, если они даже выиграют этот чемпионат, вот вообще.

😢2💩1🥱1

14 Jun 2026, 19:12 UTC18 views4 reactionsread 11 August 2026

А и просто фан-факт: Бразилия забила в первом туре столько же сколько Кюрасао и Катар. Думайте.

👍2🤔1🤝1

14 Jun 2026, 19:09 UTC18 views4 reactionsread 11 August 2026

Нуль полных матчей на ЧМ просмотрено пока. Был близок ночью, когда смотрел Бразилию и Марокко, но там на последних 10 минутах тупо вырубило. Сейчас Германию посмотрел минут 80. Да и после первого тайма больше фоном футбич был. Пару сенсаций за эти дни уже было. Это радует. Не такой очевидный турнир пока получается на старте. Но это только первый тур идет, так что еще поглядим-поглядим.

😢2👀1custom 51953826954079215691

11 Jun 2026, 06:17 UTC21 views4 reactionsread 11 August 2026

Сегодня старт Чемпионата Мира. Считанной количество матчей в удобное время. Почти все ночью или рано утром. Все матчи, как в Катаре, посмотреть не получится. Я ведь тогда реально все матчи посмотрел. Ужас. Традиционно болею за Англию. Чуть-чуть буду притапливать за Португалию и Узбекистан. Еще жду прорыва от Бразилии и Германии, их давно не было в высоких стадиях плей-офф. Ну, а сегодня Мексика выиграют ЮАР. Почти

👍2👀1🤝1

30 May 2026, 19:04 UTC28 views4 reactionsread 11 August 2026

История схожа с пенальти в финале кубка России. Тогда все говорили, что если дойдут до пенальти, то заберут победу точно «Краснодар», так как Агкацев монстр на пенальти (что правда, но только не в послематчевых сериях). В итоге Агкацев не берет ни одного удара и «Краснодар» проигрывает. Сейчас в финале ЛЧ говорили плюс минус тоже самое, но уже про Сафонова. И тут-то все сработало, правда Сафонов не взял ни одного, н

custom 519538269540792156921🤝1

30 May 2026, 15:36 UTC24 views4 reactionsread 11 August 2026

Финал ЛЧ в 19:00 – лучшее, что могли сделать УЕФА с этим финалом.

🥱2🔥1🤝1

Showing the 12 most recent of 20 posts we hold for @baiichik. 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.

Forward network

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.

Mentions

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.

Cite this entry

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Байчик🎙️” (@baiichik), 27 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/baiichik.

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.