Telegram RegisterThe public register of Telegram
Telegram profile photo for ПЕРЕЕЕЕЕЕЕЗД 🐠 : 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆

Channel

ПЕРЕЕЕЕЕЕЕЗД 🐠 : 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆

@lichbonteam

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

40subscribers

-6 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-1003953212928
TypeChannel
Username@lichbonteam
CreatedBetween 1 April 2026 and 8 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/lichbonteam

Growth

4046437 August 2026 — 46 subscribers10 August 2026 — 46 subscribers16 August 2026 — 45 subscribers22 August 2026 — 40 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -6. 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 39–47 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 18:2740-5
16 Aug 2026, 03:3845-1
10 Aug 2026, 14:3046no change
7 Aug 2026, 19:3646first reading

Engagement

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

What this channel posts

Video runtime
14s
Average length
14s

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

143 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 11.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53259827252098801721711.9%
1711.9%
custom 52290643744039983511510.5%
custom 53978428581263536611510.5%
custom 5456140674028019486149.79%
custom 5350798230202379613128.39%
custom 5402088721061267987128.39%
custom 5352873953536801333117.69%
🍌74.90%
custom 544495650617480279064.20%
custom 544266767085812414953.50%
🙏53.50%
🆒42.80%
🐳32.10%

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 8 of the 16 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 143reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 8 July 2026 to 30 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.

Recent posts

30 Jul 2026, 11:31 UTC37 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed бэйдингер 🫧 #парадокс #латте

30 Jul 2026, 11:25 UTC39 views5 reactionsread 10 August 2026

привет. мы личбон просим прощения за неактив.мы будем стараться выпускать интересный контент каждый день. совсем скоро у нас будут результаты, ждете? Надеемся на то что вам понравилось наше новое развлекательное видео. Всех обнимаем, продюссерская команда Личбон💞

custom 540208872106126798721🐳1custom 53978428581263536611

Signed бэйдингер 🫧 #парадокс #латте

30 Jul 2026, 11:24 UTC38 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed бэйдингер 🫧 #парадокс #латте

30 Jul 2026, 11:24 UTC37 views8 reactionsread 10 August 2026
Video

🐠: 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆 !! 𝐕𝗂𝖽𝖾𝗈 𝗍𝗁𝖾 𝖻𝖾𝗌𝗍 🍋 🌟 у лuчбон новое вugео в тuк токе 🍌 𝖶𝖾 𝗌𝖺𝗏𝖾𝖽 𝗒𝗈𝗎𝗋 𝗌𝗎𝗆𝗆𝖾𝗋 !! 🏝

2🆒2custom 54020887210612679872🍌1custom 53978428581263536611

Signed бэйдингер 🫧 #парадокс #латте

30 Jul 2026, 11:12 UTC33 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed бэйдингер 🫧 #парадокс #латте

13 Jul 2026, 09:49 UTC148 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed ݂₊ ׄ. 𝓜ꪮ𝐧rꪮꫀׁׅ › ׄ ִֺ۪

13 Jul 2026, 09:49 UTC165 views24 reactionsread 10 August 2026
Photo

🐠: 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆 !! 𝐈𝗇𝗍𝖾𝗋𝖺𝖼𝗍𝗂𝗏𝖾 𝗍𝗁𝖾 𝖻𝖾𝗌𝗍 🍋 🌟 к𝖺н𝖺лы 𝗇р𝗈д𝗈в Л𝗎чб𝗈н / 𝐋𝗂𝖼h𝖻𝗈𝗇 🍌 𝐌𝗂𝗒𝖾 𝐌𝗂𝖼𝗁𝗂𝖾 𝐌𝗈𝗇𝗋𝗈𝖾 🏝 𝐀𝗇𝗂𝗍𝖺 𝐑𝗈𝗌𝖾𝗅𝗂𝗒𝖺 𝐂𝗁𝖾𝖾𝗌𝖾𝖼𝖺𝗄𝖾

custom 52290643744039983517custom 53978428581263536614custom 54561406740280194864custom 53507982302023796132custom 53528739535368013332custom 54426676708581241492custom 54449565061748027902custom 53259827252098801721

Signed beidinger

10 Jul 2026, 16:44 UTC154 views25 reactionsread 10 August 2026
Photo

🐠: 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆 !! 50 𝗌𝗎𝖻𝗌𝖼𝗋𝗂𝖻𝖾𝗋𝗌🍋 🌟 н𝖺𝖼 𝗇𝗈л 𝖼𝗈тн𝗎 !! 𝖼𝗇𝖺𝖼𝗎б𝗈 к𝖺ж𝗀𝗈𝗆𝗒🍌

custom 53507982302023796138custom 54561406740280194864custom 53259827252098801723🐳2custom 535287395353680133321🍌1🆒1

Signed aнuта

9 Jul 2026, 20:05 UTC263 views16 reactionsread 10 August 2026
Poll

— npuзнаваūmeсь , вы nogaлu ?

  1. • ДАА27%
  2. • НЕЕТ27%
  3. • Я арmucm, жgy набора на npogюсupoванue27%
  4. • Кноnka Личбон😜20%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

5custom 54561406740280194864custom 54020887210612679873🍌1custom 53259827252098801721custom 53528739535368013331custom 54426676708581241491

Signed 사렁`«Thαt𝖦𝗂rľ»

9 Jul 2026, 15:52 UTC246 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed 사렁`«Thαt𝖦𝗂rľ»

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

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

9 Jul 2026, 20:05 UTCAnonymous Poll49 voters

— npuзнаваūmeсь , вы nogaлu ?

  1. • ДАА27%
  2. • НЕЕТ27%
  3. • Я арmucm, жgy набора на npogюсupoванue27%
  4. • Кноnka Личбон😜20%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

8 Jul 2026, 11:33 UTCAnonymous Poll90 voters

Кmo ваша фавka в ЛuчБон?

  1. ㊀Оm512%
  2. ㊁Aнuma23%
  3. ㊂Muйе19%
  4. ㊃Чuзkeūk18%
  5. ㊄Poзелuя33%
  6. ㊆Мuчи26%
  7. ㊇Кноnka Lichbon !! ( ot5 )11%

The shares total 142%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 16 most recent posts we hold, published 8 July 2026 to 30 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 379,504 of 1,625,954entries 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.

Forward network

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.

Mentions

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.

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

“ПЕРЕЕЕЕЕЕЕЗД 🐠 : 𝐋𝗂𝖼h𝖻𝗈𝗇 \ 𝐓𝖾𝖺𝗆” (@lichbonteam), 40 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/lichbonteam.

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.