Telegram RegisterThe public register of Telegram
Telegram profile photo for Poltorashka

Channel

Poltorashka

@po11torashka

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

28subscribers

+6 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-1003385526207
TypeChannel
Username@po11torashka
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live4 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/po11torashka

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 64% 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

2228259 August 2026 — 22 subscribers11 August 2026 — 22 subscribers4 October 2026 — 28 subscribers9 August 20264 October 2026
3 measurements spanning 56 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 21–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 14:1628+6
11 Aug 2026, 12:3322no change
9 Aug 2026, 19:4522first reading

Engagement

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

What this channel posts

Video runtime
46s
Average length
15s

Measured directly from 3 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

69 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 27.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52784909997802977081927.5%
custom 54091648471851531881217.4%
custom 5231007451968475296913.0%
custom 5291819228192602598913.0%
custom 536381788668930053568.70%
custom 527180367127591069557.25%
custom 542254024722327384557.25%
custom 545164648896899060334.35%
custom 542270652258717013611.45%

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

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

7 Aug 2026, 17:59 UTC23 views14 reactionsread 11 August 2026
Photo

🤩🤩🤩🤩🤩🤩🤩🤩 🤩🤩🤩🤩 👍🌟🤍 🤩🤩🤩🤩 😀😁😂🤣 🤩 😃😄😅😆 😉😊😋😎 😍 😘😗😀

custom 52784909997802977085custom 54091648471851531883custom 52918192281926025982custom 52718036712759106951custom 53638178866893005351custom 54227065225871701361custom 54516464889689906031

Signed Poltorashka

1 Aug 2026, 19:02 UTC48 views14 reactionsread 11 August 2026
Photo

Сегодня с китайцами 🪦

custom 52784909997802977085custom 52310074519684752962custom 52718036712759106952custom 53638178866893005352custom 54091648471851531882custom 54225402472232738451

Signed Poltorashka

31 Jul 2026, 13:13 UTC48 views14 reactionsread 11 August 2026
Photo

🥹Backstage🤩 🥹🥹

custom 52918192281926025984custom 52310074519684752962custom 52784909997802977082custom 53638178866893005352custom 54516464889689906032custom 54091648471851531881custom 54225402472232738451

Signed Poltorashka

31 Jul 2026, 07:02 UTC44 views14 reactionsread 11 August 2026
Video message

Video message, posted without a caption

custom 52784909997802977084custom 52918192281926025983custom 54091648471851531883custom 52310074519684752962custom 53638178866893005351custom 54225402472232738451

Signed Poltorashka

30 Jul 2026, 13:30 UTC46 views13 reactionsread 11 August 2026
Photo

⭐⭐⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐⭐⭐ ⭐⭐⭐⭐⭐⭐⭐⭐

custom 52310074519684752963custom 52784909997802977083custom 54091648471851531883custom 52718036712759106952custom 54225402472232738452

Signed Poltorashka

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

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

“Poltorashka” (@po11torashka), 28 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/po11torashka.

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.