Ну что, сдаём второй генетический тест, потому что одного мне не хватило.😒
🤣6custom 53008691881417258272

Channel
@freeym3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
661subscribers
+197 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001792191911 |
|---|---|
| Type | Channel |
| Username | @freeym3 |
| Created | Between 1 January 2022 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/freeym3 |
Other / unclassifiable — 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 75% 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 |
|---|---|---|
| 18 Sept 2026, 11:59 | 661 | +28 |
| 11 Sept 2026, 00:41 | 633 | +164 |
| 1 Sept 2026, 05:16 | 469 | +5 |
| 31 Aug 2026, 23:15 | 464 | first reading |
12 posts held, back to 20 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 1 page of 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 30 August 2026 |
|---|---|
| Posts held | 12 (20 August 2026 – 30 August 2026) |
| Views total | 5,644 |
| Reactions total | 193 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 31 Aug 2026, 23:15 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.
272 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 23.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5449779372196128269 | 64 | 23.5% | |
| custom 5449693859397266147 | 61 | 22.4% | |
| 🤣 | 52 | 19.1% | |
| custom 5300869188141725827 | 38 | 14.0% | |
| custom 5399889766525215511 | 28 | 10.3% | |
| custom 5474330058095075305 | 22 | 8.09% | |
| custom 5334671465524525937 | 7 | 2.57% |
Custom emoji. 6 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 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 11 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 272 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 20 August 2026 to 30 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.
Ну что, сдаём второй генетический тест, потому что одного мне не хватило.😒
🤣6custom 53008691881417258272
Как видите, я знаю её наизусть. 😏
🤣13
Video message, posted without a caption
custom 544977937219612826915🤣9custom 53008691881417258276custom 54496938593972661474
Сестра сказала, что я женская версия Распутина…
custom 544969385939726614719custom 539988976652521551111custom 530086918814172582710custom 54497793721961282697
Зовите, могу вместе с вами постоять в берёзовой рощице в тёмных одеждах и грустно помолчать 🍎🍎
custom 544977937219612826923custom 544969385939726614716custom 539988976652521551113
Поразительный список… Делитесь своими 🎧
custom 54497793721961282696custom 53008691881417258274custom 53998897665252155114
Если вдруг какие-то документы нужно подписать, можете обращаться.
custom 54496938593972661476🤣4custom 53008691881417258274
Video message, posted without a caption
custom 53008691881417258277custom 54496938593972661474
С Днём Государственного флага России, дорогие подписчики! 🇷🇺
custom 547433005809507530522🤣6custom 54497793721961282696custom 54496938593972661472
Video message, posted without a caption
🤣14custom 53008691881417258275
Представьте, перед вами стоит выбор: Не есть ничего или есть сосиски со вкусом колы. Что вы выберете?
Попробуйте найти в своём городе самую тихую улицу с неизвестными жизнями внутри, пройдитесь по ней в вечернем солнце и вам точно станет легче ✨
custom 544969385939726614710custom 53346714655245259377custom 54497793721961282697
Showing the 12 most recent of 12 posts we hold for @freeym3. 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.
Named by 1 registered channel — 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“проезд оплачен” (@freeym3), 661 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/freeym3.
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.