Telegram RegisterThe public register of Telegram
Telegram profile photo for 33bite

Channel

33bite

@urchin33bite

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

37subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003689330732
TypeChannel
Username@urchin33bite
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/urchin33bite

Growth

363736.59 August 2026 — 37 subscribers10 August 2026 — 37 subscribers17 August 2026 — 36 subscribers31 August 2026 — 37 subscribers9 August 202631 August 2026
4 measurements spanning 22 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 36–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 19:2637+1
17 Aug 2026, 21:0436-1
10 Aug 2026, 21:3237no change
9 Aug 2026, 12:1637first reading

Engagement

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

What this channel posts

Video runtime
16s
Average length
8s

Measured directly from 2 videos 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

166 reactions across 16 posts, in 7 distinct kinds. The most used accounts for 28.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53439671577325351654828.9%
custom 53616310912056180304828.9%
custom 52534681294717806222816.9%
custom 53731741379361670591810.8%
custom 5267229840343320591137.83%
custom 530983066746961228595.42%
custom 535277561596557261721.20%

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 16 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 166 reactions 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 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.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @urchin33bite. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 16 most recent posts we hold for this entry, published 12 July 2026 to 27 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

27 Jul 2026, 16:50 UTC28 views3 reactionsread 10 August 2026
Forwarded from @asteroidd333Photo

💜💜➖-➖-➖ 💜💜➖➖➖➖ > мне оч зашло рисовать френдам арты на бумажках, так шо постепенно улучшаю их оформление ➖➖➖ 🍄 🍄 🍄 > с прошедшим, мой друн трилобит ! ! ! 🤩🤩🤩 ➖➖➖➖💜💜💜💜💜 💜💜💜💜💜

custom 53616310912056180303

25 Jul 2026, 12:26 UTC20 views3 reactionsread 10 August 2026
Forwarded from @dorkdusyaVideo

С ДНЕМ РОЖДЕНИЯ ТРИЛОБИТТТ ЖРУУУГ! взяла себе челлендж заспидранить подарочек (и по совместительству атаку) с твинингом ^___^ 🎉🎉🎉 #арт

custom 53439671577325351653

25 Jul 2026, 12:25 UTC28 views1 reactionsread 10 August 2026
Forwarded from @mittenBudPhoto

картинка другу на дршку!!! развлекалась кисточками как могла пока рисовала, оч забавно и быстро получилось оно☺️

custom 52672298403433205911

22 Jul 2026, 18:48 UTC56 views10 reactionsread 10 August 2026
Photo

🗡 Быстрая защита

custom 53098306674696122856custom 53616310912056180302custom 52672298403433205911custom 53527756159655726171

22 Jul 2026, 11:23 UTC46 views12 reactionsread 10 August 2026
Forwarded from @myamlinkPhoto

С рождеством! Кастую заморозку на @urchin33bite

custom 53616310912056180307custom 53439671577325351653custom 52672298403433205911custom 53731741379361670591

21 Jul 2026, 19:24 UTC56 views13 reactionsread 10 August 2026
Photo

🍓 Быстрые атаки со стадиков

custom 536163109120561803010custom 52534681294717806222custom 53731741379361670591

21 Jul 2026, 11:54 UTC52 views20 reactionsread 10 August 2026
Photo

🤩 Февральская работа, которой я очень горжусь #арт

custom 52534681294717806229custom 52672298403433205918custom 53731741379361670592custom 53616310912056180301

21 Jul 2026, 11:39 UTC42 views13 reactionsread 10 August 2026
Photo

💀 Самая моя ленивая атака meh

custom 537317413793616705910custom 52534681294717806221custom 53098306674696122851custom 53439671577325351651

18 Jul 2026, 16:17 UTC51 views11 reactionsread 10 August 2026
Photo

🦈 Быстрая атака

custom 53439671577325351659custom 52534681294717806221custom 53098306674696122851

18 Jul 2026, 14:52 UTC237 views13 reactionsread 10 August 2026
Photo

🤩 Прошлогодняя работа с этими же персонажами #арт

custom 525346812947178062210custom 52672298403433205911custom 53098306674696122851custom 53731741379361670591

16 Jul 2026, 18:05 UTC379 views16 reactionsread 10 August 2026
Photo

🤩 Днерождевственнская атака #арт

custom 534396715773253516511custom 53616310912056180303custom 52534681294717806222

16 Jul 2026, 13:51 UTC69 views16 reactionsread 10 August 2026
Photo

😨 Сикс севаан

custom 536163109120561803012custom 52534681294717806222custom 52672298403433205911custom 53527756159655726171

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

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

“33bite” (@urchin33bite), 37 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/urchin33bite.

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.