Telegram RegisterThe public register of Telegram
Telegram profile photo for яойный укус

Channel

яойный укус

@biteyaoi

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

185subscribers

-9 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-1001640117168
TypeChannel
Username@biteyaoi
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/biteyaoi

Topic

Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 82% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

185194189.57 August 2026 — 194 subscribers8 August 2026 — 194 subscribers21 August 2026 — 190 subscribers3 September 2026 — 189 subscribers26 September 2026 — 186 subscribers7 October 2026 — 185 subscribers7 August 20267 October 2026
6 measurements spanning 61 days, net -9. 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 184–195 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 12:36185-1
26 Sept 2026, 11:56186-3
3 Sept 2026, 21:00189-1
21 Aug 2026, 09:37190-4
8 Aug 2026, 11:48194no change
7 Aug 2026, 12:21194first reading

Engagement

10 posts held, back to 19 August 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 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 10 posts for this entry, the most recent from 25 August 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3227.4%
⚡2017.1%
custom 54247750217865792021815.4%
❤1815.4%
❤‍🔥1311.1%
💋1311.1%
💘21.71%
🙏10.855%

Custom emoji. One 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 count beside it is 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 9 of the 10 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 117 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 19 August 2025 to 25 August 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.

Recent posts

25 Aug 2025, 19:55 UTC157 views7 reactionsread 8 August 2026
Photo

ого что вытворяет #ликург #хср #хонкай #старрейл #яойный #хорни яойный укус

custom 54247750217865792026❤1

24 Aug 2025, 10:33 UTC154 views10 reactionsread 8 August 2026
Photo

доброе утро 💕 как думаете с кем это он так? #вельт #хонкай #хонкайимпакт #хср #старрейл #яойчик #хорни фулл конечно же в комментах👇🏻 яойный укус

custom 54247750217865792025❤3❤‍🔥2

22 Aug 2025, 20:16 UTC113 views16 reactionsread 8 August 2026
Photo

сладких снов подписчики #дотторе #дилюк #доттолюк #генш #хот #яой #хорни яойный укус

🔥9⚡3💋3❤1

22 Aug 2025, 13:46 UTC109 views10 reactionsread 8 August 2026
Photo

я бы залетел на стримчанский #тоджи #мб #магичка #хот #горячо #ничетакойпресс #хорни #стрим #стример фулл в коммы яойный укус

⚡4💘2🔥2🙏1custom 54247750217865792021

22 Aug 2025, 08:51 UTC97 viewsread 8 August 2026

t.me/anonaskbot?start=62xE9yOB8VSmT4h подписчики чего желаете, пишите не стесняйтесь

22 Aug 2025, 08:49 UTC95 views16 reactionsread 8 August 2026
Photo

на попика засмотрелся #хикару #ёсики #летокогдапогассвет #ёсикару #канон #яой #хорни #пупсы яойный укус

🔥6custom 54247750217865792024❤2💋2⚡1❤‍🔥1

21 Aug 2025, 18:01 UTC83 views17 reactionsread 8 August 2026
Photo

фаенон еще чуть-чуть и сделает самоотсос #фаенон #мидей #фаедеи #хср #хонкай #старрейл #хорни #гимнаст фулл в комментах👇🏻 яойный укус

❤8❤‍🔥4💋4⚡1

21 Aug 2025, 09:17 UTC88 views13 reactionsread 8 August 2026
Photo

нормально так его под хвост #блейд #даньхен #renheng #хср #яой #хорни #хот яойный укус

🔥7⚡3❤‍🔥2💋1

19 Aug 2025, 19:07 UTC101 views12 reactionsread 8 August 2026
Photo

такие мальчишки желают вам спокойной ночи #мистеррека #река #скот #хср #хот #хорни #яой #напарные #яойные #горячо яойный укус

🔥5💋3custom 54247750217865792022⚡1❤1

19 Aug 2025, 16:15 UTC96 views16 reactionsread 8 August 2026
Photo

кому они зашли? #варка #кирилл #флинс #геншин #яой #интересно #хот #генш #канон яойный укус

⚡7❤‍🔥4🔥3❤2

Showing the 10 most recent of 10 posts we hold for @biteyaoi. 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.

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

“яойный укус” (@biteyaoi), 185 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/biteyaoi.

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.