Telegram RegisterThe public register of Telegram
Telegram profile photo for TYULLECHKA++

Channel

TYULLECHKA++

@tyullechka

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

246subscribers

+10 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-1001970982176
TypeChannel
Username@tyullechka
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/tyullechka

Topic

Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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

233246239.57 August 2026 — 236 subscribers8 August 2026 — 236 subscribers16 August 2026 — 233 subscribers30 August 2026 — 234 subscribers8 September 2026 — 237 subscribers17 September 2026 — 239 subscribers1 October 2026 — 236 subscribers12 October 2026 — 246 subscribers7 August 202612 October 2026
8 measurements spanning 66 days, net +10. 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 231–248 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 15:10246+10
1 Oct 2026, 01:19236-3
17 Sept 2026, 06:56239+2
8 Sept 2026, 10:19237+3
30 Aug 2026, 21:03234+1
16 Aug 2026, 04:15233-3
8 Aug 2026, 10:01236no change
7 Aug 2026, 11:15236first reading

Engagement

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

Reaction mix

22 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 95.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54674426098845085592195.5%
custom 543817813724864732414.55%

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

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

8 Aug 2026, 01:48 UTC44 viewsread 8 August 2026

ну бля я щас обоссусь какие они пиздатые, тока блять я что зимой уже в них гонять буду…..

8 Aug 2026, 01:47 UTC44 viewsread 8 August 2026

бля тока ждать походу месяца 3, потому что они винтаж и их ток под заказ мне будут делать. Еще и доставка…..

8 Aug 2026, 01:46 UTC46 views1 reactionsread 8 August 2026

кароче заказала первые

custom 54674426098845085591

8 Aug 2026, 01:00 UTC51 viewsread 8 August 2026
Poll

ааа

  1. 150%
  2. 250%

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

7 Aug 2026, 06:52 UTC76 views1 reactionsread 8 August 2026

я просто хочу факать хоу и хочу ролекс

custom 54381781372486473241

7 Aug 2026, 01:27 UTC78 views3 reactionsread 8 August 2026

музыка спасет мир

custom 54674426098845085593

30 Jul 2026, 19:02 UTC144 views9 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 54674426098845085599

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

8 Aug 2026, 01:00 UTCAnonymous Poll16 voters

ааа

  1. 150%
  2. 250%

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 12 most recent posts we hold, published 30 July 2026 to 8 August 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.

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

“TYULLECHKA++” (@tyullechka), 246 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/tyullechka.

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.