Telegram RegisterThe public register of Telegram
Telegram profile photo for MARAUDER’s crew / мародёры

Channel

MARAUDER’s crew / мародёры

@marauders_crew

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

64subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003235341226
TypeChannel
Username@marauders_crew
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/marauders_crew

Growth

636463.58 August 2026 — 63 subscribers10 August 2026 — 63 subscribers23 August 2026 — 64 subscribers6 September 2026 — 63 subscribers14 September 2026 — 64 subscribers8 August 202614 September 2026
5 measurements spanning 37 days, net +1. 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 63–64 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 11:5864+1
6 Sept 2026, 18:1663-1
23 Aug 2026, 12:3764+1
10 Aug 2026, 03:4663no change
8 Aug 2026, 18:4763first reading

Engagement

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

What this channel posts

Video runtime
1m 06s
Average length
22s

Measured directly from 3 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.

Reaction mix

176 reactions across 14 posts, in 20 distinct kinds. The most used accounts for 22.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3922.2%
🔥3017.0%
🍓1810.2%
😍179.66%
❤‍🔥169.09%
💋126.82%
👀116.25%
💯63.41%
🤝42.27%
🍌31.70%
🏆31.70%
💔31.70%
😭31.70%
👏21.14%
👾21.14%
💘21.14%
😈21.14%
🌚10.568%
👌10.568%
🥰10.568%

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 176 reactions 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 23 June 2026 to 23 July 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

23 Jul 2026, 21:06 UTC135 views19 reactionsread 10 August 2026
Photo

У НАС ТЫЩА И ВОСЕМЬ ТЫЩ! 🥳

8🍓5🔥5👌1

22 Jul 2026, 13:15 UTC181 views13 reactionsread 10 August 2026
Photo

ВНИМАНИЕ! ЗАМЕЧЕНА ПОДОЗРИТЕЛЬНАЯ МАГИЧЕСКАЯ АКТИВНОСТЬ ПРЯМО В МОСКВА-СИТИ🤩 23.07 | 19:00 Оставьте здравый смысл маглам Собираем своих, достаем палочки и устраиваем очередную шалость🫣 MARAUDER’S CREW × CORTIS - ACAI 🦁 🤩I solemnly swear that I am up to no good🤩

🔥6😍3👏21🌚1

11 Jul 2026, 20:47 UTC97 views16 reactionsread 10 August 2026
Video message

Video message, posted without a caption

😍10💋3🔥3

11 Jul 2026, 14:47 UTC250 views15 reactionsread 10 August 2026

Уже сегодня направляем всю нашу силу на защиту Хогвартса 👹😣 Приходите посмотреть и поддержать 😞

💯6👀32❤‍🔥2🔥2

6 Jul 2026, 09:02 UTC653 views13 reactionsread 10 August 2026

Мы перешагнули все красные флаги и превратили их в танец🚦 Премьера кавера на REDRED — сегодня в 15:00. Ждём вас на той стороне забора🤩🤩

6🔥4❤‍🔥3

4 Jul 2026, 18:35 UTC77 views7 reactionsread 10 August 2026
Forwarded from @shflmngPhoto

they called me a freak, 홀린 듯이, yeah 만들던 tracks, yeah, 듣고 모인 friends, yeah

💋3👾21👀1

4 Jul 2026, 15:49 UTC62 views8 reactionsread 10 August 2026
Forwarded from @bamrdamrVideo

As many as 5 redflags 5 Reasons to cancel MARAUDER'S CREW at cover dance

4🔥2😍2

4 Jul 2026, 14:11 UTC72 views7 reactionsread 10 August 2026
Forwarded from @leooncesaiddPhoto

redred done!!

3😭3🔥1

4 Jul 2026, 14:11 UTC62 views8 reactionsread 10 August 2026
Photo

тут можно увидеть как мы постепенно сходим с ума

🤝42🔥2

3 Jul 2026, 17:59 UTC266 views10 reactionsread 10 August 2026
Video

ВНИМАНИЕ ПРЯМО НА ХОГВАРТС🤩🤩 04.07 | 12:00–16:00 | Красный октябрь They called me a freak — А мы собираем своих в один грузовик, выезжаем на пустые улицы и делаем то, что другие называют «red flag» You should come mess with the team — готовьтесь перепрыгивать забор и перестать оглядываться🚦🚦 Шалость удастся с MARAUDER'S CREW🔥🦁

❤‍🔥4🏆3👀3

27 Jun 2026, 21:02 UTC179 views20 reactionsread 10 August 2026
Photo

ЭКСТРЕННОЕ УВЕДОМЛЕНИЕ ИЗ ЗАЛА ПРИЁМА🦉 Отдел: Личные Шалости и Гриффиндорские интриги Кому: Всем агентам Ордена, а также волкаи, петардам и смотрителям Дата: 28.06 Статус: ☀️ ВЫСОЧАЙШАЯ ВАЖНОСТЬ Сегодняшний день отмечен особой важностью - наш огненный волк отмечает свой личный праздник . Лео — это не просто участник Ордена, это редчайшее магическое сочетание стихий. В ней живет огонь мощного заклинания Incendio, к

🍓8🔥5👀4💘2🥰1

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

Forward network

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.

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

“MARAUDER’s crew / мародёры” (@marauders_crew), 64 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/marauders_crew.

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.