Новые фотографии
custom 54134237281659331908custom 53009744534951811854custom 52603006450506264952

Channel
@mat03er
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
236subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002063723932 |
|---|---|
| Type | Channel |
| Username | @mat03er |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/mat03er |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 20:58 | 236 | +1 |
| 15 Aug 2026, 09:18 | 235 | -3 |
| 8 Aug 2026, 09:50 | 238 | no change |
| 7 Aug 2026, 12:48 | 238 | first reading |
9 posts held, back to 6 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 9 (6 July 2026 – 4 August 2026) |
| Views total | 124 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:50 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.
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.
117 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 34.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5413423728165933190 | 40 | 34.2% | |
| custom 5300974453495181185 | 27 | 23.1% | |
| custom 5260300645050626495 | 24 | 20.5% | |
| custom 5199569914859367436 | 13 | 11.1% | |
| custom 5434121252874756456 | 7 | 5.98% | |
| custom 5371074117971745503 | 4 | 3.42% | |
| custom 5213305508034783384 | 2 | 1.71% |
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 9 of the 9 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 117reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 6 July 2026 to 4 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.
Новые фотографии
custom 54134237281659331908custom 53009744534951811854custom 52603006450506264952
Потратил в Кузне 200к, но всё равно выебнусь перед этим нищим 2️⃣0️⃣2️⃣6️⃣
custom 541342372816593319011custom 53009744534951811856custom 52603006450506264954
🇪🇸🇪🇸🇪🇸
custom 53009744534951811854custom 52603006450506264953custom 54134237281659331903
Video message, posted without a caption
custom 54134237281659331905custom 52603006450506264952custom 53009744534951811852
💔
custom 54341212528747564566
Берегитесь, я ебанутый
custom 52603006450506264955custom 51995699148593674361custom 53009744534951811851custom 54134237281659331901
Покажите реакциями, стоит ли мне покупать билеты в Новокузнецк за 40 тысяч ₽ в одну сторону
custom 519956991485936743612custom 53009744534951811856custom 54134237281659331906custom 53710741179717455034custom 52603006450506264953custom 52133055080347833842
7️⃣💔
custom 52603006450506264952custom 54341212528747564561
Чёрный диплом символизирует навыки выживания и жизненные приоритеты человека, прошедшего через трудности.
custom 54134237281659331906custom 53009744534951811854custom 52603006450506264953
Showing the 9 most recent of 9 posts we hold for @mat03er. 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“Матозер популярный?” (@mat03er), 236 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/mat03er.
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.