Telegram RegisterThe public register of Telegram
Telegram profile photo for Пекубулки |Вязаная пекарня🧁

Channel

Пекубулки |Вязаная пекарня🧁

@pekubulkifrogs

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

1,505subscribers

-4 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002427138465
TypeChannel
Username@pekubulkifrogs
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/pekubulkifrogs

Growth

1,5051,5101,507.58 August 2026 — 1,509 subscribers8 August 2026 — 1,509 subscribers10 August 2026 — 1,510 subscribers14 August 2026 — 1,505 subscribers8 August 202614 August 2026
4 measurements spanning 6 days, net -4. 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 1,504–1,511 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:081,505-5
10 Aug 2026, 16:531,510+1
8 Aug 2026, 02:151,509no change
8 Aug 2026, 01:021,509first reading

Engagement

16 posts held, back to 26 June 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 1,505 subscribers
Avg views / post
385
8 posts measured
Reaction rate
7.60%
reactions ÷ views · ER floor
Posts in window
10
of 16 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (26 June 20267 August 2026)
Views total3,078
Reactions total234
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:02 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video 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

483 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 581196055108492400216133.3%
custom 577365597974482587810621.9%
6613.7%
custom 57763019415921669485511.4%
🥰5110.6%
custom 5775997222252450027398.07%
👍40.828%
🍓10.207%

Custom emoji. 4 of the rows above are 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 14 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 483reactions 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 26 June 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, 08:07 UTC137 views19 reactionsread 8 August 2026
Photo

Добрый пятничный денечек 🩵 Вы понимаете что нас ждет… просто вау!🌟 Так горжусь собой и этими крылышками) 🤩🤩 🤩🤩 Поближе покажу чуть позже 🩷

custom 577599722225245002714custom 57736559797448258785

6 Aug 2026, 11:59 UTC182 views29 reactionsread 8 August 2026
Photo

Модифицируем обувь) Такие милые получились ❤🥺

custom 5811960551084924002148custom 57763019415921669484custom 57736559797448258782custom 57759972222524500271

1 Aug 2026, 15:40 UTC388 views32 reactionsread 8 August 2026
Photo

А это я леплю)

custom 581196055108492400232

1 Aug 2026, 14:31 UTC358 views21 reactionsread 8 August 2026
Photo

Какие же тапочки мииииилашные❤️ Этот июль просто жила в режиме ожидания… появились задержки на вб( В связи с этим, не могу планировать свои доходы и решила делать 2-3 заказа в месяц по вашему референсу, остальное на наличие. Очень много времени уходит на поиск материалов для индивидуальных заказов, их ожидание и поправки. Моя особенность в том, что я на гипер фокусе делаю заказ и он должен появиться здесь и сейчас.

custom 581196055108492400215custom 577630194159216694832custom 57736559797448258781

27 Jul 2026, 16:30 UTC504 views23 reactionsread 8 August 2026
Photo

Я тут тронулась умом по алоказиям) Поставила тепличку и закинула клубни 🩵 Покажите, что выращиваете? Это похоже уже возраст 😂

19custom 57736559797448258784

25 Jul 2026, 13:01 UTC420 views37 reactionsread 8 August 2026
Photo

Какая я молодец, что выложила эту схему рисунка сюда, весь интернет перерыла и потом у себя и нашла) 🩷✨

custom 577365597974482587823custom 57759972222524500277custom 58119605510849240024custom 57763019415921669483

21 Jul 2026, 09:20 UTC574 views49 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 577365597974482587834custom 581196055108492400274custom 57763019415921669484

19 Jul 2026, 15:14 UTC515 views24 reactionsread 8 August 2026
Photo

Немного ирла) Я осуществила свою мечту, впервые покаталась на сапах!!!!( озеро Донцо вроде называется ) Очень теперь надеюсь на еще одни теплые выходные и на наличие бензина. Как кстати у вас с этим всем? Кто откуда? поделитесь погодой, фотками с отдыха и как у вас с бензином?

custom 581196055108492400215custom 57736559797448258785👍4

16 Jul 2026, 08:28 UTC652 views48 reactionsread 8 August 2026
Photo

Весь день вчера пыталась выложить красотулю…🥰 Я не понимаю почему именно в канал не могу выкладывать, а с другими общаюсь в тг норм

custom 581196055108492400232custom 577630194159216694812custom 57736559797448258784

9 Jul 2026, 18:20 UTC716 views33 reactionsread 8 August 2026
Photo

Кажется тут не хватает наших милашек🩵 Покажите ваших любимцев 🩵

custom 5811960551084924002285

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

Citation-graph rank

Citation-graph rank — 907,281 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 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.

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

“Пекубулки |Вязаная пекарня🧁” (@pekubulkifrogs), 1,505 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/pekubulkifrogs.

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.