5 лайков и не доделаю
custom 534358340669959052622custom 53348672000691122308custom 53349279480865477418

Channel
@perro764
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
85subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003670950604 |
|---|---|
| Type | Channel |
| Username | @perro764 |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/perro764 |
Memes & entertainment — 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 27 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 20:15 | 85 | +2 |
| 9 Sept 2026, 03:59 | 83 | +4 |
| 30 Aug 2026, 09:28 | 79 | +6 |
| 24 Aug 2026, 04:15 | 73 | +2 |
| 16 Aug 2026, 03:05 | 71 | -1 |
| 9 Aug 2026, 22:46 | 72 | no change |
| 7 Aug 2026, 12:42 | 72 | +1 |
| 6 Aug 2026, 21:18 | 71 | first reading |
12 posts held, back to 3 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.
359 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 35.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5343583406699590526 | 126 | 35.1% | |
| custom 5334867200069112230 | 101 | 28.1% | |
| custom 5334927948086547741 | 73 | 20.3% | |
| custom 5337286005391135507 | 59 | 16.4% |
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 12 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 359 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 3 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.
5 лайков и не доделаю
custom 534358340669959052622custom 53348672000691122308custom 53349279480865477418
рофланы
custom 534358340669959052615custom 53372860053911355079custom 53349279480865477417custom 53348672000691122301
маленький вкусненький малышочек ааа #Arcane_Zine #ArcaneSPOILER_Zine
custom 534358340669959052615custom 53348672000691122309custom 53372860053911355075
hel' unleashed😈
custom 533486720006911223019custom 53435834066995905268custom 53349279480865477415custom 53372860053911355071
летняя практика в так называемое высшее образовательное учреждение
custom 533728600539113550716custom 53348672000691122305custom 53349279480865477414
2-3 years in dagestan
custom 533486720006911223018custom 53435834066995905268custom 53372860053911355075
Posted without readable text
custom 534358340669959052619custom 53348672000691122302custom 53349279480865477412
🙂🙂нас 67 праздник
custom 533492794808654774119custom 53435834066995905269custom 53372860053911355073custom 53348672000691122302
hey nana i still think about you🙂
custom 533486720006911223018custom 53349279480865477418custom 53372860053911355075
что делают с человеком 26 часов в поезде
custom 533492794808654774114custom 53435834066995905269custom 53372860053911355077
моя очень умная глубокая вселенная маддогов
custom 533486720006911223015custom 53349279480865477416custom 53435834066995905265custom 53372860053911355071
get jjjjinxed😍
custom 534358340669959052616custom 53372860053911355077custom 53348672000691122304
Showing the 12 most recent of 12 posts we hold for @perro764. 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.
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.
Named by 4 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“maddog” (@perro764), 85 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/perro764.
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.