Telegram RegisterThe public register of Telegram
Telegram profile photo for # hoodie weather 🌿 arch

Channel

# hoodie weather 🌿 arch

@impepperr

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

38subscribers

+0 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-1001607095553
TypeChannel
Username@impepperr
Description:: мы разрисуем все заборы своими стихами, достань, пожалуйста, краску из рюкзака
Created15 May 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live23 August 2026
Measurements held2
On Telegramt.me/impepperr

Growth

387 August 2026 — 38 subscribers10 August 2026 — 38 subscribers7 August 202610 August 2026
2 measurements spanning 3 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 37–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:0138no change
7 Aug 2026, 19:5238first reading

Engagement

19 posts held, back to 13 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 19 posts for this entry, the most recent from 5 August 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2,040
Videos
236
Links
186

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

150 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52513491171619726165738.0%
custom 53350135338998307154731.3%
custom 53527753754474021954630.7%

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

Measured over the 19 most recent posts we hold, published 13 July 2024 to 5 August 2024, 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

5 Aug 2024, 12:58 UTC160 viewsread 10 August 2026

нежно напоминаю о том, что сменила канальчик🥺

Signed paprika

16 Jul 2024, 09:34 UTC206 views5 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 52513491171619726163custom 53350135338998307151custom 53527753754474021951

Signed paprika

15 Jul 2024, 20:39 UTC186 views6 reactionsread 10 August 2026
Photo

Photo, posted without a caption

custom 52513491171619726164custom 53350135338998307151custom 53527753754474021951

Signed paprika

15 Jul 2024, 19:55 UTC117 views7 reactionsread 10 August 2026

снова попадаю в ловушку длинный картинок по песням. ай.

custom 53350135338998307155custom 52513491171619726161custom 53527753754474021951

Signed paprika

15 Jul 2024, 16:48 UTC114 views5 reactionsread 10 August 2026

когда-нибудь я научусь их рисовать хорошо, я обещаю.

custom 52513491171619726163custom 53350135338998307151custom 53527753754474021951

Signed paprika

15 Jul 2024, 16:48 UTC113 views18 reactionsread 10 August 2026
Photo

для отчетности! спонтанно нарисованное подружке вчера и на удивление неплохое #ppr_arts

custom 525134911716197261610custom 53350135338998307154custom 53527753754474021954

Signed paprika

15 Jul 2024, 16:19 UTC100 views4 reactionsread 10 August 2026
Photo

флетмейтки красиво опустошали казну (ходили по магазинам и залипали на все подряд) 👏🏻

custom 52513491171619726164

Signed paprika

14 Jul 2024, 20:17 UTC76 views8 reactionsread 10 August 2026

чтение яблочного спаса фобс это момент, когда оплата у психолога прошла.

custom 52513491171619726164custom 53527753754474021953custom 53350135338998307151

Signed paprika

14 Jul 2024, 18:38 UTC77 views12 reactionsread 10 August 2026

рисование в тишине, разговоры в градации от трепетных тем до часового разбора громверса, кино в наушниках на двоих по дороге домой... душевно 🫂

custom 53350135338998307157custom 52513491171619726163custom 53527753754474021952

Signed paprika

14 Jul 2024, 11:16 UTC82 views10 reactionsread 10 August 2026
Photo

тэгнулась 🖐🏻

custom 53350135338998307156custom 52513491171619726163custom 53527753754474021951

Signed paprika

Showing the 12 most recent of 19 posts we hold for @impepperr. 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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“# hoodie weather 🌿 arch” (@impepperr), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/impepperr.

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.