Channel
@yamz007
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
303subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001508360451 |
|---|---|
| Type | Channel |
| Username | @yamz007 |
| Created | 4 November 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/yamz007 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 00:37 | 303 | -5 |
| 4 Sept 2026, 20:18 | 308 | -1 |
| 28 Aug 2026, 12:33 | 309 | +2 |
| 21 Aug 2026, 22:15 | 307 | -1 |
| 15 Aug 2026, 01:53 | 308 | +1 |
| 8 Aug 2026, 07:49 | 307 | no change |
| 7 Aug 2026, 20:03 | 307 | first reading |
4 posts held, back to 15 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 4 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
116 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463163765895761694 | 44 | 37.9% | |
| custom 5269496822866410195 | 37 | 31.9% | |
| custom 5463312835620670652 | 35 | 30.2% |
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 4 of the 4 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 15 July 2026 to 28 July 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.
а веееедь я так и не поделилась с вами нашим с пашей комиксом, хотя эмбарго уже как месяц В С Ё кто пропустил - мы второй раз участвовали в конкурсе уё историй у виталия и с этой работой смогли пройти😉 спасибо всем, кто поддерживал и верил, дальше больше!🤩
custom 546316376589576169417custom 546331283562067065215custom 526949682286641019511
15.07 вылезли вкусно покушать и закинуть денег в лудку
custom 546316376589576169411custom 52694968228664101957custom 54633128356206706524
14.07 показали диане и дамиру выборг им вроде понравилось🌚 поднялись наконец на башню (соня обосралась) и съели закрытый бургер (соня обосралась), о котором мечтали с прошлой поездки
custom 546316376589576169411custom 54633128356206706528custom 52694968228664101957
11-13.07 вышла на работу не понравилось🌟 ну чучуть тока за пару дней поздравила двух именинников наташу и андрея, только вперед, мои старые подростки, ни шагу назад!
custom 526949682286641019512custom 54633128356206706528custom 54631637658957616945
Showing the 4 most recent of 4 posts we hold for @yamz007. 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“маша ямз оо7” (@yamz007), 303 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/yamz007.
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.