❄️Т492ТТ99-455т.₽. ТТТ 📝 @EDUARD555 ☎️ 8(916)561-30-40
❤1

Channel
@regznak
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
29,950subscribers
+152 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001372194984 |
|---|---|
| Type | Channel |
| Username | @regznak |
| Description | Официальный канал по покупке и продаже красивых автономеров в Москве и МО | 10 лет на рынке Размещения своего номера платное❗️ ▪️Купить-Продать номер: @EDUARD555 ▪️Телефон для связи: 8 (916) 561-30-40 ▪️Сайт: https://market-avtonomerov.net |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/regznak |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 12:33 | 29,950 | +14 |
| 26 Aug 2026, 11:07 | 29,936 | -2 |
| 25 Aug 2026, 12:02 | 29,938 | +3 |
| 24 Aug 2026, 12:03 | 29,935 | +18 |
| 22 Aug 2026, 16:15 | 29,917 | +12 |
| 21 Aug 2026, 04:26 | 29,905 | +17 |
| 20 Aug 2026, 07:52 | 29,888 | +5 |
| 19 Aug 2026, 10:23 | 29,883 | +7 |
| 18 Aug 2026, 09:27 | 29,876 | +13 |
| 17 Aug 2026, 09:54 | 29,863 | +17 |
| 15 Aug 2026, 15:37 | 29,846 | +9 |
| 14 Aug 2026, 05:28 | 29,837 | +13 |
| 12 Aug 2026, 19:33 | 29,824 | +1 |
| 11 Aug 2026, 20:17 | 29,823 | +8 |
| 10 Aug 2026, 17:31 | 29,815 | +8 |
| 8 Aug 2026, 15:27 | 29,807 | +9 |
| 7 Aug 2026, 09:30 | 29,798 | no change |
| 7 Aug 2026, 09:24 | 29,798 | first reading |
110 posts held, back to 3 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 49 pagesof 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. It is computed over the 86 of 109 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 110 (3 August 2026 – 27 August 2026) |
| Views total | 319,396 |
| Reactions total | 235 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 21:02 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.
Lifetime counters from Telegram’s own channel header, read 27 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
235 reactions across 72 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 235 | 100.0% |
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 86 of the 110 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 235reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 110 most recent posts we hold, published 3 August 2026 to 27 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.
❄️Т492ТТ99-455т.₽. ТТТ 📝 @EDUARD555 ☎️ 8(916)561-30-40
❤1
✔️М006УМ777-400т.₽. 📝 @EDUARD555 ☎️ 8(916)561-30-40
❤2
🪆М888АТ77-2м.₽. МАТ 📌ШАХ и МАТ👑 📝 @EDUARD555 ☎️ 8(916)561-30-40
🔒С300СЕ777-300т.₽. ССЕ 👑Купил себе Land Cruiser 300,а номер триста нет?!🫵 ⚠️Фатальная ошибка‼️ ✏️ @EDUARD555 ☎️ 8(916)561-30-40
🗣️Е009УС97-400т.₽. 📨 @EDUARD555 ☎️ 8(916)561-30-40
❤2
🪆К888НР777-1.5м.₽. КНР 🇨🇳Китайская Народная Республика🇨🇳 📨@EDUARD555 ☎️ 8(916)561-30-40
❤2
⚠️В333КВ150-400т.₽. ВКВ ✏️ @EDUARD555 ☎️ 8(916)561-30-40
➡️К003ВВ50-300т.₽. КВВ ✏️ @EDUARD555 ☎️ 8(916)561-30-40
⭐️Х050АМ77-775т.₽. ХАМ 🖕ХАМоватая зеркалка,на старой Москве👍 ✏️ @EDUARD555 ☎️ 8(916)561-30-40
❤3
🚨О516ОО77-1.7м.₽. ООО ✏️ @EDUARD555 ☎️ 8(916)561-30-40
❤2
📿А007УЕ190-525т.₽. АУЕ ☝🏻номера для тех,кто живёт по понятиям,АУЕ👊🏻 ✏️ @EDUARD555 ☎️ 8(916)561-30-40
❤3
💥О799СО799-425т.₽. ОСО 📝 @EDUARD555 ☎️ 8(916)561-30-40
❤3
Showing the 12 most recent of 110 posts we hold for @regznak. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“Купить госномера Москва красивые автономера продать” (@regznak), 29,950 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/regznak.
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.