Telegram RegisterThe public register of Telegram

Channel

Mav коллит ☎️

@mavcalls

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

251subscribers

+0 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-1002395695945
TypeChannel
Username@mavcalls
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/mavcalls

Growth

2517 Aug 2026, 15:55 — 251 subscribers8 Aug 2026, 09:31 — 251 subscribers7 Aug 2026, 15:558 Aug 2026, 09:31
2 measurements taken within a single day. 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 250–252 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 09:31251no change
7 Aug 2026, 15:55251first reading

Engagement

20 posts held, back to 1 December 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
145
Links
127

Lifetime counters from Telegram’s own channel header, read 8 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.

Reaction mix

31 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 32.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 58730676320804567211032.3%
custom 5866369239740320716722.6%
custom 5884500392640780142722.6%
custom 5776343456746050867619.4%
custom 581462295836203980413.23%

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 8 of the 20 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 31reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 December 2025 to 16 March 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

16 Mar 2026, 10:29 UTC333 views6 reactionsread 8 August 2026
Photo

Видел как после $THE, все сразу начали искать нужный парсер, где быстрее заколлил и тд.. поэтому решил сделать пост Вчера гуляя с девушкой, телефон разрывался от уведов Pengu Mirror, пока с телефона я понял в чем дело, уже было поздно, успел только зашортить в конце, в итоге + 579 Но пост не про профит в 579 баксов, а для тех у кого нет возможности оплачивать все парсера/приватки, сам к таким отношусь и юзаю Ведь

custom 58845003926407801423custom 58663692397403207162custom 58730676320804567211

31 Dec 2025, 21:11 UTC511 views7 reactionsread 8 August 2026

С новым годом! ❤️ Прям перед НГ устроили раздачу денег, лично я закрыл в +2400, очень приятный подарок. Желаю чтоб у каждого этот год получился мега продуктивным, все цели были достигнуты, а планы перевыполнены! 🍷

custom 58730676320804567215custom 58663692397403207161custom 58845003926407801421

25 Dec 2025, 11:47 UTC576 views4 reactionsread 8 August 2026
Photo

+1057 (дали вывести) 😊 всем кому накинули рк соболезную, самому очень повезло

custom 58663692397403207163custom 58730676320804567211

4 Dec 2025, 11:31 UTC615 views2 reactionsread 8 August 2026

30 минут до дропа 🚬

custom 58730676320804567212

4 Dec 2025, 09:53 UTC566 views2 reactionsread 8 August 2026
Photo

GM, снова секретный дроп Binance Alpha, работаем 👊 На кошелек ранее закинули $ESPORTS, возможно он и будет, возьму небольшой шорт Закиньте кошельки в @ray_red_bot (@drops работает через раз), либо можно трекать парсер @alphasecretdrop

custom 57763434567460508672

3 Dec 2025, 22:57 UTC443 views3 reactionsread 8 August 2026
Photo

умер от фомо 😣

custom 58146229583620398041custom 58730676320804567211custom 58845003926407801421

3 Dec 2025, 15:38 UTC392 viewsread 8 August 2026

сука раг 🤲 перезашел, стоп откинул 0.15, если выбьет перезаходить больше не буду

3 Dec 2025, 15:13 UTC379 viewsread 8 August 2026

идет шилл монеты $SAPIEN, в связи с тем, что команда Трампа обращает внимание на робототехнику команда $SAPIEN занимается обучением ИИ, mcap всего 40M взял лонг, твх 0.157, пока посижу, стоп уже в бу

3 Dec 2025, 11:03 UTC334 viewsread 8 August 2026
Photo

GM, всем кто вчера не заработал дают второй шанс, сегодня в 16:00 будет снвоа секретный дроп от Binance Alpha 🚬 Кошельки у вас есть, добавьте их в @drops, так же использую @alphasecretdrop, ибо вчера drops bot не прислал увед

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

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Mav коллит ☎️” (@mavcalls), 251 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/mavcalls.

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.