ищите на схеме. дом моды метрополитена
❤15🔥2😁2custom 54674716653382734821

Channel
@piauer_metro
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
58subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003110315568 |
|---|---|
| Type | Channel |
| Username | @piauer_metro |
| Description | 📍 Край магнолий vk.com/piauer |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/piauer_metro |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 06:01 | 58 | no change |
| 7 Aug 2026, 19:14 | 58 | first reading |
14 posts held, back to 3 January 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 3 August 2026 |
|---|---|
| Posts held | 14 (3 January 2026 – 3 August 2026) |
| Views total | 74 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 06:01 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 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 videos 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.
293 reactions across 14 posts, in 21 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 92 | 31.4% | |
| 😈 | 53 | 18.1% | |
| ❤🔥 | 49 | 16.7% | |
| custom 5467810048631658566 | 20 | 6.83% | |
| 🔥 | 20 | 6.83% | |
| 🍾 | 9 | 3.07% | |
| 💋 | 9 | 3.07% | |
| custom 5242407884309938624 | 6 | 2.05% | |
| 🍓 | 6 | 2.05% | |
| 😁 | 5 | 1.71% | |
| 😍 | 5 | 1.71% | |
| 🏆 | 4 | 1.37% | |
| 🫡 | 4 | 1.37% | |
| custom 5467579245679107352 | 2 | 0.683% | |
| 🍌 | 2 | 0.683% | |
| 💘 | 2 | 0.683% | |
| custom 5467471665338273482 | 1 | 0.341% | |
| ⚡ | 1 | 0.341% | |
| 💅 | 1 | 0.341% | |
| 🤝 | 1 | 0.341% | |
| 1 further kind | 1 | 0.341% |
Custom emoji. 4 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 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 14 of the 14 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 293reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 3 January 2026 to 3 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.
ищите на схеме. дом моды метрополитена
❤15🔥2😁2custom 54674716653382734821
дорогие подписчики поздравляю вас с прошедшим началом лета и желаю качественно отдохнуть!! дети. защищать.
❤11😈6🍾2💅1💋1
ищите на схеме. дом моды метрополитена.
❤🔥13❤4😈1custom 54678100486316585661
дорогие друзья, сегодня на нашей подземной улице праздник поздравляю вас со всероссийским днём метрополитена держитесь правой стороны, уступайте места поездам
😈14❤🔥9❤5💋1
с праздником Победы, дорогие друзья именно в этот день рекомендую к просмотру великолепный фильм «Зеркало для героя» не забывайте о бабушках и дедушках не забывайте об истории 🔥
❤12🫡4🏆3❤🔥1
ищите на схеме. дом моды метрополитена.
❤14🔥5😈4custom 52424078843099386242🏆1🤩1
представляю вашему вниманию первый заказ на дизайн футболки, отчеканенный в железнодорожных подземельях человеком в красной шапке ищите на схеме. дом моды метрополитена.
❤🔥13😍5💋4❤1🍌1🤝1custom 52424078843099386241custom 54675792456791073521
любимые подружаечки подписчицы, тысяча и одно поздравление с весной и восьмым марта!! 💗 💗 💗 не прекращайте быть самыми красивыми и целовательными 🍎💗 ниже привожу полный список пожеланий 📦
custom 546781004863165856614❤7🍓3😈2custom 52424078843099386241
поздравляю всех влюблённых с профессиональным праздником!! в честь такого события с гордостью представляю сделанные в подземельях метрополитена пикчи для ITMOcraft метрополитен.лендлиз
❤🔥8💘2😈2❤1
❤️🐄 С днём святого Валентина! 🐄❤️ Хотите порадовать свою вторую половинку? А может быть, вы только планируете признаться кому-то в любви? Для вас мы подготовили эти цифровые валентинки ❤️ Сохраняйте картинку и отправляйте её тем, кому хотите заявить о своих чувствах! Пускай сегодня стрелы Купидона попадут куда надо 😚
🔥13❤6🍓3😈1
itmo.marketing
😈8❤3💋1
готовимся... метрополитен. фотографировать.
🍾7⚡1❤🔥1😈1custom 54675792456791073521
Showing the 12 most recent of 14 posts we hold for @piauer_metro. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“метрополитен” (@piauer_metro), 58 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/piauer_metro.
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.