@METRO_DJINFI ЛС

Channel
🐊METRO SHOP DJINFI 24/7🐊
@metroDjinfi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · 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 | -1003316012502 |
|---|---|
| Type | Channel |
| Username | @metroDjinfi |
| Created | Between 1 November 2025 and 25 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/metroDjinfi |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 08:20 | 52 | -2 |
| 23 Aug 2026, 03:13 | 54 | -1 |
| 15 Aug 2026, 20:16 | 55 | +10 |
| 10 Aug 2026, 15:15 | 45 | no change |
| 7 Aug 2026, 17:54 | 45 | first reading |
Engagement
14 posts held, back to 25 November 2025 — 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 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 10 December 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 1m 36s
- Average length
- 48s
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.
Reaction mix
90 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 36.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5429424809215797643 | 33 | 36.7% | |
| custom 5224454641839780913 | 19 | 21.1% | |
| custom 5409368119397328267 | 12 | 13.3% | |
| 👎 | 10 | 11.1% | |
| ❤ | 9 | 10.0% | |
| 🔥 | 7 | 7.78% |
Custom emoji. 3 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 9 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 90 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 25 November 2025 to 10 December 2025, 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
продам все за 250 рублей🔥
@METRO_DJINFI ЛС
фул 6 10₽ мк вк 10₽ JS9 10₽ все с обвесами
Video, posted without a caption
@METRO_DJINFI 🔥🔥🔥🔥🔥🔥
custom 54294248092157976436custom 52244546418397809133custom 54093681193973282672
🔥сегодня акция снижение цен🔥 🔥🔥🔥🔥🔥🔥🔥5️⃣0️⃣➗ на все в ассортименте
custom 54294248092157976436custom 52244546418397809132custom 54093681193973282671
@METRO_DJINFI ЛС СО МНОЙ
custom 54294248092157976435custom 52244546418397809134custom 54093681193973282672
ещё есть 3 мк золото цены в личные сообщения
custom 54294248092157976436custom 52244546418397809134custom 54093681193973282672
🔥сыграть со мной тдм-метро 25🤑⭐️
❤3👎3custom 54294248092157976432custom 52244546418397809131custom 54093681193973282671
🔥МАСШТАБНЫЙ РОЗЫГРЫШ НА 30 ФУЛ ШЕСТЫХ СЕТОВ НА 3 ПОБЕДИТЕЛЯ🔥
👎5🔥4custom 54294248092157976434❤1custom 52244546418397809131custom 54093681193973282671
весь инвентарь за 2000 рублей 🔥
❤3👎1custom 52244546418397809131custom 54093681193973282671custom 54294248092157976431
Showing the 12 most recent of 14 posts we hold for @metroDjinfi. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“🐊METRO SHOP DJINFI 24/7🐊” (@metroDjinfi), 52 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/metroDjinfi.
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.