Telegram RegisterThe public register of Telegram
Telegram profile photo for mezzo piano

Channel

mezzo piano

@m3zz0p1an0

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

52subscribers

-7 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003836285434
TypeChannel
Username@m3zz0p1an0
Created28 February 2026measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/m3zz0p1an0

Growth

525955.57 August 2026 — 59 subscribers10 August 2026 — 59 subscribers14 August 2026 — 56 subscribers29 August 2026 — 55 subscribers6 September 2026 — 54 subscribers13 September 2026 — 52 subscribers7 August 202613 September 2026
6 measurements spanning 36 days, net -7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 51–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 03:2052-2
6 Sept 2026, 03:1654-1
29 Aug 2026, 04:4355-1
14 Aug 2026, 19:2456-3
10 Aug 2026, 05:4659no change
7 Aug 2026, 18:4659first reading

Engagement

19 posts held, back to 28 February 2026the 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 19 posts for this entry, the most recent from 3 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

39 reactions across 5 posts, in 10 distinct kinds. The most used accounts for 20.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5314352134160948189820.5%
custom 5208729847446132084717.9%
custom 5440536924697681621615.4%
custom 5438638824030758312512.8%
🍓37.69%
custom 520861120326954934525.13%
custom 520886867796901004625.13%
custom 520888477980140335525.13%
custom 531432826273271495225.13%
custom 531442958960116162125.13%

Custom emoji. 9 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 5 of the 19 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 28 February 2026 to 3 June 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.

Recent posts

3 Jun 2026, 07:28 UTC174 viewsread 10 August 2026

газан 67, подай заявку в чат, куда ты потерялся, мы скучаем

20 Mar 2026, 17:29 UTC533 views5 reactionsread 10 August 2026

по поводу этого писать владельцу — @rayttqw

custom 53143521341609481893custom 52086112032695493452

20 Mar 2026, 16:24 UTC473 views12 reactionsread 10 August 2026

🤩🤩🤩🤩🤩 🤩🤩обрый день! mezzo piano нуждается в наборе админов - и вот список, кто нам нужен! 🤩🤩. админ по чату (0/3)— принимает заявки, вливает участников кф. Следит за чатом, чтобы не было нарушений, и поднимает актив в группе. 🤩🤩. админ по нью (0/2) — рекламирует кф, тем самым ищет новых участников. Принимает заявки и вливает нью. 🤩🤩. младший админ (0/2) — следит за чатом, помогает с чисткой, вливает участников

custom 53143521341609481894custom 52087298474461320842custom 52088686779690100462custom 52088847798014033552custom 53143282627327149522

6 Mar 2026, 15:40 UTC≈7,100 views7 reactionsread 10 August 2026
Photo

🤩🤩🤩🤩🤩 мы новая кф по скз без анкет и иниц по желанию! здесь вы найдёте много друзей и новых знакомств!🤩 🤩🤩🤩🤩🤩🤩🤩🤩🤩 чтобы вступить в чат, нужно лишь выполнить следующие условия: О1. подписаться на наше инфо и прочитать правила. О2. подать заявку на чат, а ссылка на него находится в навигации. О3. после принятия заявки искать новые знакомства, общаться и веселиться! 🤩🤩🤩🤩🤩🤩🤩🤩🤩 🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾 🤩🤩🤩🤩🤩🤩🤩🤩

custom 52087298474461320845custom 53144295896011616212

4 Mar 2026, 16:54 UTC641 viewsread 10 August 2026

🤩🤩🤩🤩🤩🤩🤩🤩🤩 🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾 ᶠʳᵒᵐ ᵐᵉᶻᶻᵒ ᵖᶦᵃᶰᵒ ᵐᵉᶻᶻᵒ ᵖᶦᵃᶰᵒ ᵃᵈᵐ ᶫᵒᵛᵉ ᵐᵉᶻᶻᵒ ᵖᶦᵃᶰᵒ ᵐᵉᶻᶻᵒ ᵖᶦᵃᶰᵒ ᵇᵉˢᵗ ᵐᵉᶻᶻᵒ ᵖᶦᵃᶰᵒ @m3zz0p1an0 копируется при нажатии! ставить по желанию! 🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾🐾

Showing the 12 most recent of 19 posts we hold for @m3zz0p1an0. 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.

Mentions

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.

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.

Cite this entry

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.

“mezzo piano” (@m3zz0p1an0), 52 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/m3zz0p1an0.

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.