Telegram RegisterThe public register of Telegram
Telegram profile photo for @ Biscuit INFO

Channel

@ Biscuit INFO

@biscuitrelate

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

5subscribers

-1 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002838607459
TypeChannel
Username@biscuitrelate
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 11 September 2026
On Telegramt.me/biscuitrelate

Growth

565.513 August 2026 — 6 subscribers14 August 2026 — 6 subscribers21 August 2026 — 5 subscribers13 August 202621 August 2026
3 measurements spanning 8 days, net -1. 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 5–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 03:525-1
14 Aug 2026, 17:566no change
13 Aug 2026, 11:326first reading

Engagement

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

Reaction mix

113 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 15.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53933556609791202771815.9%
custom 53955854533803818781513.3%
custom 53955928407241298221513.3%
custom 53956147579422401181311.5%
custom 53505227638849221231210.6%
custom 53953697558278065871210.6%
custom 5395684572635635476119.73%
custom 535051690984449956997.96%
custom 539350457179023802487.08%

Custom emoji. Every row above is a 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 are Telegram’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 14 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 113 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 12 July 2026 to 27 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

27 Jul 2026, 13:09 UTC78 views17 reactionsread 13 August 2026

хелло чмоня дни + лив с гскм, возможно на время, но не точно. 🌸 искл : ризз и сфп киллуа связь со мной возможна через соо кн всех целукаю🌸

custom 53953697558278065875custom 53505227638849221234custom 53955928407241298222custom 53956845726356354762custom 53505169098444995691custom 53933556609791202771custom 53935045717902380241custom 53956147579422401181

12 Jul 2026, 17:52 UTC187 views5 reactionsread 13 August 2026

❌❌ᶻ 𝗓 𐰁

custom 53505169098444995692custom 53956147579422401182custom 53933556609791202771

12 Jul 2026, 17:51 UTC185 views10 reactionsread 13 August 2026

🌸 🐏 𝖶𝗂𝗇𝗌 𝗈𝗇 𝗕𝗜𝗠𝗜

custom 53933556609791202772custom 53953697558278065872custom 53955854533803818782custom 53955928407241298222custom 53505227638849221231custom 53956845726356354761

12 Jul 2026, 17:50 UTC185 views15 reactionsread 13 August 2026

Posted without readable text

custom 53505169098444995693custom 53956147579422401183custom 53505227638849221232custom 53935045717902380242custom 53955854533803818782custom 53955928407241298222custom 53933556609791202771

12 Jul 2026, 17:50 UTC175 views16 reactionsread 13 August 2026
Poll

😕

  1. ❌🔹ilty . . 🥹23%
  2. 🥹 🔹nno . .77%

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

custom 53933556609791202773custom 53505227638849221232custom 53935045717902380242custom 53955854533803818782custom 53955928407241298222custom 53956147579422401182custom 53956845726356354762custom 53953697558278065871

12 Jul 2026, 17:47 UTC175 views16 reactionsread 13 August 2026
Photo

🥹 🌟🤩🤩🤩 𝗅𝗂𝗌𝗍. . 🎁🌸 @ 𝖬𝗒 𝗌𝗐𝖾𝖾𝗍 𝖻𝖾𝗅𝗈𝗏𝖾𝖽 𝗱𝗲𝗮𝗿 𝖡𝗂𝗌𝖼𝗎𝗂𝗍 ! 🌸 ❗️ | @.𝖪𝗂𝗅𝗅𝘂𝗮 ! 🏹 | @.𝖫𝖺𝘁𝘁𝖾 . . | @. au𝗮 | @.𝗋𝗂𝘇𝘇💕| @.Miz𝘂❤️! | @. 𝗋𝖺𝗏𝖾𝗰𝗵𝗮𝗻 (*ˊᗜˋ*)

custom 53955854533803818783custom 53956845726356354763custom 53505169098444995692custom 53933556609791202772custom 53953697558278065872custom 53955928407241298222custom 53505227638849221231custom 53956147579422401181

12 Jul 2026, 17:47 UTC164 views16 reactionsread 13 August 2026
Photo

🌸🥹🔹𝗽𝘁𝗶𝗼𝗻 . . 🥹

custom 53933556609791202774custom 53956147579422401183custom 53935045717902380242custom 53955854533803818782custom 53955928407241298222custom 53956845726356354762custom 53505169098444995691

Showing the 12 most recent of 14 posts we hold for @biscuitrelate. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

12 Jul 2026, 17:50 UTCAnonymous Poll44 voters

😕

  1. ❌🔹ilty . . 🥹23%
  2. 🥹 🔹nno . .77%

Shares as published. No per-option vote count is published by Telegram, so none is 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 14 most recent posts we hold, published 12 July 2026 to 27 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.

Mentions

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.

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

“@ Biscuit INFO” (@biscuitrelate), 5 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/biscuitrelate.

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.