Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘱𝘢𝘵𝘤𝘩𝘣𝘳𝘦𝘢𝘬𝘦𝘳𝘴 𝘤𝘧 & 𝘥𝘢𝘪𝘭𝘺

Channel

𝘱𝘢𝘵𝘤𝘩𝘣𝘳𝘦𝘢𝘬𝘦𝘳𝘴 𝘤𝘧 & 𝘥𝘢𝘪𝘭𝘺

@patchbreakersduocf

2 usernames

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

746subscribers

+342 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004336355733
TypeChannel
Usernames@patchbreakersconfession @patchbreakersduocf
Descriptioncr : amiisev on twt
CreatedBetween 1 June 2026 and 4 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 October 2026
Measurements held11
On Telegramt.me/patchbreakersduocf

Topic

Gaming — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

4047465758 August 2026 — 404 subscribers8 August 2026 — 404 subscribers15 August 2026 — 450 subscribers22 August 2026 — 516 subscribers28 August 2026 — 556 subscribers4 September 2026 — 582 subscribers11 September 2026 — 596 subscribers19 September 2026 — 612 subscribers3 October 2026 — 721 subscribers6 October 2026 — 746 subscribers6 October 2026 — 746 subscribers8 August 20266 October 2026
11 measurements spanning 59 days, net +342. 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 353–797 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 09:22746no change
6 Oct 2026, 08:47746+25
3 Oct 2026, 23:54721+109
19 Sept 2026, 13:17612+16
11 Sept 2026, 23:56596+14
4 Sept 2026, 07:00582+26
28 Aug 2026, 05:37556+40
22 Aug 2026, 04:15516+66
15 Aug 2026, 12:44450+46
8 Aug 2026, 14:41404no change
8 Aug 2026, 14:16404first reading

Engagement

37 posts held, back to 4 August 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
27.7%
avg views ÷ 746 subscribers
Avg views / post
207
16 posts measured
Reaction rate
11.5%
reactions ÷ views · ER floor
Posts in window
17
of 37 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 6 October 2026
Posts held37 (4 August 2026 – 6 October 2026)
Views total3,311
Reactions total381
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Oct 2026, 09:22 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

Photos
331
Videos
97
Links
367

Lifetime counters from Telegram’s own channel header, read 6 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 22s
Average length
18s

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

749 reactions across 36 posts, in 13 distinct kinds. The most used accounts for 45.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤33845.1%
❤‍🔥10313.8%
👀10013.4%
💘7910.5%
🥰608.01%
😇253.34%
🕊152.00%
🔥141.87%
💊101.34%
😭20.267%
💯10.134%
😢10.134%
🙏10.134%

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

Measured over the 37 most recent posts we hold, published 4 August 2026 to 6 October 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

6 Oct 2026, 07:01 UTC77 views15 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : aceyways on twt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersbot

💘5❤‍🔥4❤3👀2🥰1

Signed ТриМанул🍅🍅👼🏻 [мск+7]

5 Oct 2026, 16:03 UTC156 views24 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : liuhaoyu231 on tt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersbot

❤11❤‍🔥6💘5👀1🔥1

Signed .

5 Oct 2026, 13:01 UTC170 views17 reactionsread 6 October 2026
Video

ᝰ.⌗credits : lanhuannnnnn on tt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersbot

❤8❤‍🔥5💘2👀1🔥1

Signed ТриМанул🍅🍅👼🏻 [мск+7]

5 Oct 2026, 10:01 UTC175 views20 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : coxnt0ne on twt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersbot

❤‍🔥9💘6🔥3❤1👀1

Signed ТриМанул🍅🍅👼🏻 [мск+7]

5 Oct 2026, 07:39 UTCviews —

𝘱𝘢𝘵𝘤𝘩𝘣𝘳𝘦𝘢𝘬𝘦𝘳𝘴 𝘤𝘧 & 𝘥𝘢𝘪𝘭𝘺 pinned a photo

5 Oct 2026, 07:39 UTC193 views21 reactionsread 6 October 2026

не раз было,что в бота кидают просьбы о том,чтобы скинуть их бб арт/видео или даже просили им скинуть В КОММЫ НСФВ АРТЫ. причем было,что кидали тейки не один раз. НЕТ ЧУВАКИ,мы не скинем ваши рисунки,видео(и другие виды творчества) и такие просьбы в конфу.на что вы вообще надеетесь,когда в правилах прописан запрет на бб. Пожалуйста,не засоряйте нам бота подобными тейками. 🌟— бот был заменён в связи с тем,что раньше т…

❤‍🔥12❤7🥰2

Signed .

5 Oct 2026, 07:39 UTC175 views24 reactionsread 6 October 2026
Photo

🤩 реша: Доброго времени суток кф! хочу сказать о том, что у Споука имеются границы на шипперинг и в этом кф он ЗАПРЕЩЕН. в этой конфе приветствуются только платонические отношения. прошу не демонстрировать свою любовь к этому шипу в тейк-боте или в обсуждении под постами.оставьте шипперство за пределами конфы. запрещено не только шипперство,но и другие виды бб. границы предоставлены на фото выше.

❤‍🔥14❤7🥰2👀1

Signed .

5 Oct 2026, 07:01 UTC189 views28 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : rawrzcc on twt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersduo_bot

❤13🥰8❤‍🔥4👀2💘1

Signed ТриМанул🍅🍅👼🏻 [мск+7]

5 Oct 2026, 04:02 UTC196 views21 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : narkozavisimastinside on tg doomed cutest duo ever tags : #take ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersduo_bot

❤10🔥5❤‍🔥3👀2💘1

Signed .

3 Oct 2026, 16:02 UTC222 views29 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : stupidpumkin6 on tt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersduo_bot

❤17🥰7💘3👀2

Signed .

3 Oct 2026, 13:00 UTC226 views22 reactionsread 6 October 2026
Video

ᝰ.⌗credits : elylirae on tt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersduo_bot

💘10❤‍🔥5❤4👀2🙏1

Signed .

3 Oct 2026, 10:04 UTC243 views33 reactionsread 6 October 2026
Photo

ᝰ.⌗credits : happyspoke123 on tt tags : #daily ⠀⠀⠀⠀⠀ ╰┈➤ @patchbreakersduo_bot

❤15🥰8💘4🔥4❤‍🔥1👀1

Signed .

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

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

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

“𝘱𝘢𝘵𝘤𝘩𝘣𝘳𝘦𝘢𝘬𝘦𝘳𝘴 𝘤𝘧 & 𝘥𝘢𝘪𝘭𝘺” (@patchbreakersduocf), 746 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/patchbreakersduocf.

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.